You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After editing a file and applying HMR, refreshing the browser should hydrate successfully without mismatch errors — even when tag structures or text content have changed.
Actual Behavior
Hydration mismatch occurs after refreshing the browser — even if the previous HMR applied successfully.
This happens frequently when changing tag structures or text nodes in routes like _index.tsx.
SSR HTML and client-rendered React tree do not match on hydration.
I tried adding Cache-Control: no-store to the route loader, and also tested client-only rendering using useEffect, but the issue still reproduces.
If this is expected behavior for Remix + Vite development mode, I'd appreciate confirmation or best practices to avoid this issue during development.
---This issue report was prepared with the help of ChatGPT (for summarization & formatting).---
The text was updated successfully, but these errors were encountered:
Reproduction
Steps to reproduce:
pnpm dev
/
routes/_index.tsx
and change any text or tag (e.g.,)
Optional repo: [you can paste your GitHub repo link or say “not uploaded yet”]
I'm happy to prepare a repro repo if needed.
System Info
Used Package Manager
pnpm
Expected Behavior
After editing a file and applying HMR, refreshing the browser should hydrate successfully without mismatch errors — even when tag structures or text content have changed.
Actual Behavior
Hydration mismatch occurs after refreshing the browser — even if the previous HMR applied successfully.
This happens frequently when changing tag structures or text nodes in routes like
_index.tsx
.SSR HTML and client-rendered React tree do not match on hydration.
I tried adding
Cache-Control: no-store
to the route loader, and also tested client-only rendering usinguseEffect
, but the issue still reproduces.If this is expected behavior for Remix + Vite development mode, I'd appreciate confirmation or best practices to avoid this issue during development.
---This issue report was prepared with the help of ChatGPT (for summarization & formatting).---
The text was updated successfully, but these errors were encountered: