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
When a page is rendered server side and an API call responded with an error (4xx or 5xx) the state is lost during hydration, causing a hydration mismatch error.
Here's a breakdown of the events:
server renders component (by awaiting the suspense promise) and renders the error message
browser loads html with error message
component code is executed client-side
instead of keeping the error response, useQuery sets error to null and isPending to true, causing hydration mismatch errors
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
Environment
Package:
@hebilicious/vue-query-nuxt 0.3.0
Node:
v22.12.0
Reproduction
Describe the bug
When a page is rendered server side and an API call responded with an error (4xx or 5xx) the state is lost during hydration, causing a hydration mismatch error.
Here's a breakdown of the events:
error
tonull
andisPending
totrue
, causing hydration mismatch errorsAdditional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: