[Flight] Add debugChannel option to Edge and Node clients
#34236
+635
−66
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
eps1lon
approved these changes
Aug 20, 2025
unstubbable
pushed a commit
to vercel/next.js
that referenced
this pull request
Aug 20, 2025
[diff facebook/react@0bdb9206...03fda05d](facebook/react@0bdb920...03fda05) <details> <summary>React upstream changes</summary> - facebook/react#34237 - facebook/react#34236 - facebook/react#34234 - facebook/react#34225 </details>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
When a debug channel is used between the Flight server and a browser Flight client, we want to allow the same RSC stream to be used for server-side rendering. To support this, the Edge and Node Flight clients also need to accept a
debugChanneloption. Without it, debug information would be missing (e.g. for SSR error stacks), and in some cases this could result inConnection closederrors.This PR adds support for the
debugChanneloption in the Edge and Node clients for ESM, Parcel, Turbopack, and Webpack. Unlike the browser clients, these clients only support a one-way channel, since the Flight server’s return protocol is not designed for multiple clients.The implementation follows the approach used in the browser clients, but excludes the writable parts.