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

[edge] latest edge version breaks useFetch in composition API module #8781

Closed
manniL opened this issue Feb 7, 2021 · 2 comments · Fixed by nuxt-community/composition-api#366
Assignees

Comments

@manniL
Copy link
Member

manniL commented Feb 7, 2021

Cross-linking nuxt-community/composition-api#364 here for visibility / awareness (because the root cause could trigger errors in other scenarios as well) ☺️

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

Related commit: 92018e5

Please check the linked issue for repro + error scenario.

Copy link
Member

Potential backwards compatibility would be to define a push function on the object.

But I think this is an internal API and I am not sure we need to do anything apart from updating the NCA plugin. Thoughts?

@danielroe danielroe self-assigned this Feb 7, 2021
@manniL
Copy link
Member Author

manniL commented Feb 7, 2021

If we can update NCA without breaking changes this’d probably be fine 👍🏼

danielroe added a commit to nuxt-community/composition-api 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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants