Uh oh!
There was an error while loading. Please reload this page.
[Flight] allow context providers from client modules - #35675
Merged
Conversation
samselikoff
commented
Feb 3, 2026
Contributor
Closes #35340 |
rickhanlonii
requested review from
eps1lon and unstubbable
and removed request for
eps1lonFebruary 3, 2026 03:56
eps1lon
reviewed
Feb 3, 2026
Uh oh!
There was an error while loading. Please reload this page.
eps1lon
approved these changes
Feb 3, 2026
Add tests for lazy-loaded context providers to ReactLazy-test.internal.js. Update existing test that expected lazy Context to throw - it now works. Co-authored-by: Sophie Alpert <git@sophiebits.com>
Uh oh!
There was an error while loading. Please reload this page.
github-actionsBot
pushed a commit
that referenced
this pull request
Feb 3, 2026
Allows Server Components to import Context from a `"use client'` module and render its Provider. Only tricky part was that I needed to add `REACT_CONTEXT_TYPE` handling in mountLazyComponent so lazy-resolved Context types can be rendered. Previously only functions, REACT_FORWARD_REF_TYPE, and REACT_MEMO_TYPE were handled. Tested in the Flight fixture. ty bb claude Closes#35340 --------- Co-authored-by: Sophie Alpert <git@sophiebits.com> DiffTrain build for [3e00319](3e00319)
github-actionsBot
pushed a commit
that referenced
this pull request
Feb 3, 2026
Allows Server Components to import Context from a `"use client'` module and render its Provider. Only tricky part was that I needed to add `REACT_CONTEXT_TYPE` handling in mountLazyComponent so lazy-resolved Context types can be rendered. Previously only functions, REACT_FORWARD_REF_TYPE, and REACT_MEMO_TYPE were handled. Tested in the Flight fixture. ty bb claude Closes#35340 --------- Co-authored-by: Sophie Alpert <git@sophiebits.com> DiffTrain build for [3e00319](3e00319)
acdlite
reviewed
Aug 10, 2026
| // Context.Provider === Context in React, so return the same reference. | ||
| // This allows server components to render <ClientContext.Provider> | ||
| // which will be serialized and executed on the client. | ||
| return receiver; |
Collaborator
There was a problem hiding this comment.
This is a bug. This is only correct if it's a React Context object, but nothing in this path performs that check.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
Allows Server Components to import Context from a
"use client'module and render its Provider.That means you can now import Context in a server component and pass it a value for the Client to read without a client component wrapper:
Note: this is not server context. It's just creating the Context with a value from the server in the client bundle. You cannot
use(Context)in a server component.Only tricky part was that I needed to add
REACT_CONTEXT_TYPEhandling in mountLazyComponent so lazy-resolved Context types can be rendered. Previously only functions, REACT_FORWARD_REF_TYPE, and REACT_MEMO_TYPE were handled.Tested in the Flight fixture.
ty bb claude
Closes#35340