test(nextjs): ensure orchestrion stays out of client bundles - #22777
Merged
Conversation
We are already restricting orchestrion channel injections to only be active in the server bundle, but this test ensures that never slips. Webpack, Vite, and Nuxt are already covered by tests, so Turbopack was the last remaining gap.
isaacs
requested review from
a team,
mydea,
nicohrubec,
s1gr1d and
timfish
and removed request for
a team,
nicohrubec and
s1gr1d
July 28, 2026 15:12
timfish
approved these changes
Jul 29, 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
2 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.
We are already restricting orchestrion channel injections to only be active in the server bundle, but this test ensures that never slips.
Webpack, Vite, and Nuxt are already covered by tests, so Turbopack was the last remaining gap.