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
use the name as a stable useId namespace for resumed hydration
cover opposite async resolution orders and client-only work appearing during hydration
Background
#5108 assigned a numeric namespace to each Suspense boundary as it rendered. That kept sibling boundaries stable when they resolved in different orders, but the namespace still depended on render order. As described in #5135, client-only work could render during hydration and consume the namespace that a later server-rendered boundary expected, shifting its generated ids.
A named boundary no longer participates in that shared allocation order. Its name deterministically seeds the namespace on both the server and client, and the namespace is retained on the component when its VNode is replaced. Unnamed boundaries keep their existing behavior.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
nameprop toSuspenseuseIdnamespace for resumed hydrationBackground
#5108 assigned a numeric namespace to each
Suspenseboundary as it rendered. That kept sibling boundaries stable when they resolved in different orders, but the namespace still depended on render order. As described in #5135, client-only work could render during hydration and consume the namespace that a later server-rendered boundary expected, shifting its generated ids.A named boundary no longer participates in that shared allocation order. Its name deterministically seeds the namespace on both the server and client, and the namespace is retained on the component when its VNode is replaced. Unnamed boundaries keep their existing behavior.