#hydration error and FOUC in production only
1 messages · Page 1 of 1 (latest)
Hydration errors that only hit production are often date issues, since your local server is often the same timezone as your dev browser
hmmm, its happening on pages without any date objects or dates being rendered, such as the login page
Figured it out - its the Dashlane chrome extension thats causing the issues. I guess there is nothing I can do about third party extensions causing hydration issues?
Not much, and they’ll affect all SSR react sites in some way, but sometimes you can mitigate it depending on where it’s modifying the dom
Next has slightly fewer of these issues because they mount to a div in the body instead of the whole document, so any extensions that modify the head don’t cause the issue
You can use remix-islands to get that behaviour but there’s a Dan Abramov comment somewhere saying that react doesn’t recommend that as a long term strategy
I tend to consider hydration issues related to extensions as something that either React core or the extension author needs to fix and not something I focus on myself