Open salmannotkhan opened 2 months ago
Same error in Qutebrowser, working fine in Brave.
Qute Browser is also based webkit. I think this bug is only with webkit based browsers. Maybe webkit handles cached html responses differently?
I've been reading and it seems Qutebrowser uses WebEngine as backend so it's probably related to compatibility issues. Once you build are you getting any error?
No, only issues with dev server
Same here. Easy to reproduce in Safari by following steps above. Not getting it in chrome.
I had this same issue; setting NODE_ENV=development
seemed to fix the issue. Seems like this aught to be automatic in this command?
Seems like the client is rendering some kind of cached snapshot of the project, I can see remix attempting to load/display old code that has long been updated. Might be noteworthy to add that this happens only on manual reloads, if I hot reload the app (changing source code with running dev server) everything works fine, but as soon as you hit CMD+R to reload the browser window hell is let loose.
Reproduction
routes/_index.tsx
(add any html element)System Info
Used Package Manager
npm
Expected Behavior
It should render updated change without any hydration error.
Actual Behavior
Error: Hydration failed because the initial UI does not match what was rendered on the server
Because server is responding with latest code and client is rendering old code.