Add experimental.useExperimentalReact to opt into React's experimental channel#94861
Merged
Conversation
Contributor
Stats cancelledCommit: f967d06 |
Contributor
Tests PassedCommit: f967d06 |
2782ced to
f967d06
Compare
gaspar09
approved these changes
Jun 16, 2026
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
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.
Opting into React's experimental channel — which emits
<link rel="expect">to hold first paint until the streamed shell is coherent, avoiding flicker from partially-streamed HTML — currently requires enabling an unrelated feature likeexperimental.taintas a side effect, which is confusing. This addsexperimental.useExperimentalReactas a direct opt-in.It feeds the existing
needsExperimentalReactaggregation and the matching Turbopackreact_channelswitch, selecting thereact@experimentalbuild the same waytaint,transitionIndicator, andgestureTransitiondo. It's opt-in only: an explicitfalsecan't disable the channel when one of those still requires it (the taint APIs only exist in the experimental build), soassignDefaultswarns on that contradiction. Covered by a webpack e2e test mirroring the existingtaintchannel test.