Remove experimental.useNodeStreams flag as it's enabled#93938
Open
timneutkens wants to merge 1 commit into
Open
Remove experimental.useNodeStreams flag as it's enabled#93938timneutkens wants to merge 1 commit into
experimental.useNodeStreams flag as it's enabled#93938timneutkens wants to merge 1 commit into
Conversation
Contributor
Tests PassedCommit: 95ef513 |
timneutkens
force-pushed
the
codex/node-streams-always-on
branch
from
62c12c5 to
ef72214
Compare
Contributor
Stats cancelledCommit: 95ef513 |
timneutkens
changed the title
timneutkens
force-pushed
the
codex/node-streams-always-on
branch
from
af71def to
5a21522
Compare
timneutkens
force-pushed
the
codex/node-streams-always-on
branch
3 times, most recently
from
890a7bb to
25fd1f0
Compare
timneutkens
force-pushed
the
codex/node-streams-always-on
branch
from
25fd1f0 to
95ef513
Compare
timneutkens
changed the title
experimental.useNodeStreams flag as it's enabled
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What?
Remove
experimental.useNodeStreamsfrom the public config surface and make Node streams always-on for Node.js App Router rendering.The smaller default-on change and dedicated CI cleanup landed in #94311. The standalone compatibility update landed separately in #94347.
Why?
Node streams are now the default Node.js runtime rendering path, so the opt-in config and runtime selection plumbing are stale. Edge bundles continue to use the web-stream path because Node streams are unavailable there.
How?
__NEXT_USE_NODE_STREAMSas true for Node.js app runtime bundles and false for edge user bundles.experimental.useNodeStreams.experimental.useNodeStreams.Verification
pnpm --filter=next typespnpm build-all