You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 5, 2024. It is now read-only.
After upgrading to 0.10.3 I found that on server rendering useFetch() was returning undefined and therefore my destructuring would throw and error. However, all would be OK when mounting the component on the client side only.
🐛 The bug
OK this might be intentional but it might be worth a discussion
I was previously using
0.9.3
and had a composition function that looked like this:After upgrading to
0.10.3
I found that on server renderinguseFetch()
was returning undefined and therefore my destructuring would throw and error. However, all would be OK when mounting the component on the client side only.Given that the docs use the example:
I'm wondering if this is intentional, or a regression.
🛠️ To reproduce
Use the example
useFetch()
in the docs using0.10.3
and check if error 'Can not structured from undefined` shows on server render.🌈 Expected behaviour
useFetch()
always returns and object withfetch
andfetchState
properties, on both client and server.ℹ️ Additional context
I am using this inside a separate file, I don't think this matters but will detail below:
index.vue
@/data
The text was updated successfully, but these errors were encountered: