pageProps aren't updated on first page with ClientRouter
See original GitHub issuerepro:
- with vue-full example, run app with SSR+SPA mode(no prerender)
vite build && vite build --ssr
cross-env NODE_ENV=production ts-node ./server
-
access to http://localhost:3000/hello/alice and then, click /hello/eli
-
URL changes and client gets appropriate pageContext.json , but name prop will not update.
Once you change to other page(component) and back to /hello, it becomes to work correctly. So, maybe first hydration does not work well. This does not occur on dev mode.
Issue Analytics
- State:
- Created a year ago
- Comments:14 (9 by maintainers)
Top Results From Across the Web
Props of hydrated slot component is not updated on ...
When props passed to App is changed, I expect Page.vue get updated. But when Page.vue is rendered on server side, update does not...
Read more >NextJS initial state is not updating when routing to same ...
When using NextJS, getInitialProps is called before the page renders only for the first time. On subsequent page renders (client side ...
Read more >NextJS - dynamic page and dynamic folder at root level
js for the Page custom type - for pages such as /about and contact-us while I want to dynamically create folders for content,...
Read more >Advanced Features: Custom `App`
pageProps is an object with the initial props that were preloaded for your page by one of our data fetching methods, otherwise it's...
Read more >Next.js: packages/next/shared/lib/router/router.ts
As a special service "Fossies" has tried to format the requested source page into HTML format using (guessed) TypeScript source code syntax highlighting...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The issue was fixed. Next Vue patch will include it.
I couldn’t get response on forum, so I created issue.