Promote next analyze command - #99074
Merged
Merged
Conversation
Contributor
Tests PassedCommit: 28bc54b |
wbinnssmith
marked this pull request as ready for review
September 23, 2026 21:36
lukesandberg
approved these changes
Sep 23, 2026
| await exit.catch(() => {}) | ||
| } | ||
| }) | ||
| it('accepts experimental-analyze as an alias', async () => { |
Contributor
There was a problem hiding this comment.
these don't strike me as very valuable tests, trim it down?
Co-authored-by: Will Binns-Smith <[email protected]>
Co-authored-by: Will Binns-Smith <[email protected]>
Co-authored-by: Will Binns-Smith <[email protected]>
Co-authored-by: Will Binns-Smith <[email protected]>
wbinnssmith
force-pushed
the
promote-next-analyze
branch
from
September 23, 2026 23:05
dfa9f8b to
28bc54b
Compare
wbinnssmith
enabled auto-merge (squash)
September 23, 2026 23:16
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.
What?
Promote the Turbopack bundle analyzer to
next analyzeand its build-time option tonext build --analyze. Update CLI help, docs, and analyzer UI guidance to use those names, and remove the guide's experimental label. Keep both experimental spellings available for existing scripts.Why?
Users should be able to discover and use the concise analyzer names without breaking workflows that already rely on the experimental command or build flag.
How?
The standalone analyzer uses a Commander command alias, so both command names share one implementation and option set. The build flag uses a hidden compatibility option, with both spellings driving the same Turbopack-only build analysis path. The existing analyzer e2e tests exercise the primary command.