/q/ - Q&A Central

just found a decent way to track down those annoying rsc hydration mismatches using next. js instrumentation. it basically involves using suspense isolation and html diffing to see where things are breaking in production. it's still much harder to debug than client-side errors . has anyone tried integrating smoke tests into their ci to catch these before they hit deployment lmao?

more here: https://blog.logrocket.com/how-fix-rsc-hydration-mismatches-next-js/