-
Notifications
You must be signed in to change notification settings - Fork 26.7k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Missing debug tools #55526
Comments
Are you seeing this on the latest Next.js? Don't they have error sorting by framework? Like if it is a Next.js issue or a React one. With that aside, usually these hydration errors are explained fully in the console, with logs printed by React. Otherwise, it can be so many things it is hard to give a blanket statement, but if its not pretty simple, or impossible hard, like when a CDN injects HTML and then React fails to hydrate. React has also an open issue, not sure if its this one: facebook/react#26224 to make this errors clearer, and while Next.js is the go to meta-framework, I do think this is ultimately something React should help with. I had an open issue on React, but after a while, I decided to close it, with some 2023 edit notes: facebook/react#24519 (comment), hope those can help you fix your issue. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hello guys,
what I'm really missing in this framework is proper debug tools. I know the state of node, react, etc. but this is really what I would appreciate from the framework. Tooling to make me productive.
When an error like this happens on a project I don't know properly it takes me so much time to find the cause. Did you brainstorm on some solutions or tooling? Are there some ideas in the backlog to help us smash problems like this?
Describe the Bug
It's an example of general error message.
Expected Behavior
Debug bar where I can see the difference between SSR and Client, help me to identify the issue.
To Reproduce
Produce one of bug listed here: https://nextjs.org/docs/messages/react-hydration-error
The text was updated successfully, but these errors were encountered: