-
Notifications
You must be signed in to change notification settings - Fork 26.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Returning a string from a page component causes hydration mismatch error #65985
Comments
I can't reproduce this. Does it happen in incognito mode as well? or maybe I started your project wrongly? https://stackblitz.com/github/tom-sherman/next-text-page-hydration-mismatch?file=README.md |
Have you tried locally? Stackblitz isn't 100% accurate for streaming rendering. |
Did that just now, and still works fine. Tried with canary on React 19 as well, no issue. Could it be a Node.js version thing? |
I narrowed it down to a specific chrome extension: https://chromewebstore.google.com/detail/json-viewer/gbmdgpbipfallnflgajpaliibnhdgobh I may close this then, but before doing so I'm going to investigate a bit more exactly what that extension is doing to cause the mismatch. |
Probably edits the HTML with a pre tag or something like that |
This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Link to the code that reproduces this issue
https://github.com/tom-sherman/next-text-page-hydration-mismatch
To Reproduce
Current vs. Expected behavior
Current: Hydration mismatch error in dev and prod builds.
Expected: no error
Provide environment information
Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:10:42 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6000 Available memory (MB): 16384 Available CPU cores: 8 Binaries: Node: 20.9.0 npm: 10.5.0 Yarn: 1.22.19 pnpm: 9.1.0 Relevant Packages: next: 14.3.0-canary.72 // Latest available version is detected (14.3.0-canary.72). eslint-config-next: N/A react: 19.0.0-beta-04b058868c-20240508 react-dom: 19.0.0-beta-04b058868c-20240508 typescript: 5.1.3 Next.js Config: output: N/A
Which area(s) are affected? (Select all that apply)
Runtime
Which stage(s) are affected? (Select all that apply)
next dev (local), next start (local), Vercel (Deployed), Other (Deployed)
Additional context
Not sure this is a huge issue as returning a string from a route shouldn't be used that much.
The text was updated successfully, but these errors were encountered: