Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Too eager HYDRATION renders SSG pointless.
See original GitHub issueDescribe the bug
The __NEXT_REDUX_WRAPPER_HYDRATE__ action executes after the page has been rendered, not before.
So as a result, a query is already started before.
This seems to happen only if you navigate on that page - if you refresh on that page, hydration happens first and then the page renders.
To Reproduce
In this repo I’ve made a very basic app which uses SSG/SSR with RTK Query and redux-persist: https://github.com/hevar/ssr-persist-redux-nextjs
Where you can view it occouring.
Expected behavior
I expect an initial render with SSG then a hydration with revalidated data.
Issue Analytics
- State:
- Created a year ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We are seeing that working fine on initial page load (e.g. when refreshing), but not with rehydration after navigation to a SSR page, where the components render first and then the rehydration happens.
Try it yourself in https://githubbox.com/hevar/ssr-persist-redux-nextjs - just navigate from the main page to the “bulbasaur SSR” link
I’ve created a PR #498 (in addition to previously mentioned #497) where I am proposing a fix. Please have a look. Comments are welcome.