Closed xander-marjoram closed 2 months ago
In the render function, you can see that I am logging the value of the propObject
prop. I made the following observations, which may be of interest:
ssr value in Nuxt config |
Server | Client |
---|---|---|
true |
Value logged correctly | undefined |
false |
n/a | Value logged correctly |
@xander-marjoram I think this is related to this research I had done on hydration issue for complex object types with Vue.
Read more here
https://github.com/prashantpalikhe/nuxt-ssr-lit/issues/34#issuecomment-1325563509
@xander-marjoram Vue has fixed the issue on their end that causes this hydration issue for us.
https://github.com/vuejs/core/issues/7203
Can you please try again with the latest version of Vue
@prashantpalikhe Sorry for the delayed reply, this did manage to fix our issues! Thanks for letting me know
Describe the bug When using the contents of an object prop to conditionally render elements, hydration fails due to a mismatch error. A fuller description with a code example is available in this minimal reproduction: https://github.com/xander-marjoram/nuxt-lit-ssr-issue-repro
To Reproduce Steps to reproduce the behavior:
Expected behavior When SSR is enabled, the prop should have the correct value when rendering on the client. Ideally, there should then be no mismatch, and hydration should succeed without error.
Screenshots
^3.12.3
(seepackage.json
of linked repo for more deps).