[Flight] Transfer Debug Info from a synchronous Reference to another Chunk #34229
Conversation
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
github-actions
bot
added
the
React Core Team
unstubbable
approved these changes
Aug 19, 2025
This was referenced Aug 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Whatever blocks the synchronous reference also blocks the parent from resolving.
In practice the server doesn't outline anything that isn't already there so it would be rare but for client references the chunk dependency can show up like this.
This surfaces some other issue with DevTools not properly surfacing this that I'm still investigating.The issue is that these get modeled as the last debug info on the fiber which we typically consider blocking the parent Server Component or in general parent component. E.g. promise in child position of a Server Component is blocking that Server Component. So it becomes more like the parent component was awaiting the reference rather than that the<div>itself was suspended on it which isn't exactly wrong. Regardless, it properly bubbles up to the nearest Suspense as expected.