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
Expands the behavior of enableClientRenderFallbackOnHydrationMismatch to
check text content, too.
If the text is different from what was rendered on the server, we will
recover the UI by falling back to client rendering, up to the nearest
Suspense boundary.
Copy file name to clipboardexpand all lines: scripts/error-codes/codes.json
+2-1
Original file line number
Diff line number
Diff line change
@@ -408,5 +408,6 @@
408
408
"420": "This Suspense boundary received an update before it finished hydrating. This caused the boundary to switch to client rendering. The usual way to fix this is to wrap the original update in startTransition.",
409
409
"421": "There was an error while hydrating this Suspense boundary. Switched to client rendering.",
410
410
"422": "There was an error while hydrating. Because the error happened outside of a Suspense boundary, the entire root will switch to client rendering.",
411
-
"423": "This root received an early update, before anything was able hydrate. Switched the entire root to client rendering."
411
+
"423": "This root received an early update, before anything was able hydrate. Switched the entire root to client rendering.",
412
+
"424": "Text content does not match server-rendered HTML."
0 commit comments