How to see hydration errors on dev environment | Next.js | Page 1

topaz whale Oct 9, 2022, 11:45 PM

#

I keep running into hydration errors in the console of my production builds, but I don't see them in the console during development. This is making it extremely difficult to pinpoint what the cause of the error is. Is there some sort of config that allows me to see the errors in a dev environment?

tight flame Oct 10, 2022, 6:46 AM

#

I am also wondering this

old crane Oct 10, 2022, 7:26 AM

#

If you cant repro them in dev mode, I would run npm run build && npm start locally with this flag https://nextjs.org/docs/advanced-features/source-maps#configuration-flag

topaz whale Oct 10, 2022, 4:49 PM

#

old crane If you cant repro them in dev mode, I would run `npm run build` && `npm start` l...

I tried this with the flag but I still can't repro. Only in production via vercel do I see the hydration errors in console

tight flame Oct 11, 2022, 6:56 AM

#

Same for me

old crane Oct 12, 2022, 5:14 AM

#

I would probably run a build with that flag (on the production server) to help me understand what's wrong, not ideal but it might help

#How to see hydration errors on dev environment