Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: latest nuxt edge breaks useFetch #364

Closed
manniL opened this issue Feb 7, 2021 · 0 comments · Fixed by #366
Closed

fix: latest nuxt edge breaks useFetch #364

manniL opened this issue Feb 7, 2021 · 0 comments · Fixed by #366
Assignees
Labels
bug Something isn't working

Comments

@manniL
Copy link
Member

manniL commented Feb 7, 2021

🐛 The bug
When using useFetch together with the latest nuxt-edge version (tested with "nuxt-edge": "^2.15.0-26876193.fffb1a19"), an SSR error occurs (vm.$ssrContext.nuxt.fetch.push is not a function).

image

Last working version: nuxt-edge@2.15.0-26802759.5a5161aa
First broken version: nuxt-edge@2.15.0-26807078.b06df717

Related commit: nuxt/nuxt@92018e5

🛠️ To reproduce
Steps to reproduce the behavior:

  1. Check out https://github.com/manniL/capi-nuxt-edge-fetch-bug
  2. Install deps via yarn
  3. Start dev server via yarn dev
  4. Go to http://localhost:3000/
  5. Experience the error

🌈 Expected behaviour
No error in this scenario

@manniL manniL added the bug Something isn't working label Feb 7, 2021
danielroe added a commit that referenced this issue Feb 10, 2021
danielroe added a commit that referenced this issue Feb 14, 2021
* feat: support new fetchKey (Nuxt 2.15+) - closes #364, nuxt/nuxt#8781
* fix: fix issue with refetching/hydration in full static mode - closes #292
* fix: align fetch keys with 2.15 - see nuxt/nuxt#8809
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants