docs(cli): clarify that --debug-build-paths requires route group folders in paths#92618
Merged
Conversation
…ers in paths Co-authored-by: Joseph <icyJoseph@users.noreply.github.com>
Contributor
|
All broken links are now fixed, thank you! |
Co-authored-by: Joseph <icyJoseph@users.noreply.github.com>
Contributor
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
Co-authored-by: Joseph <icyJoseph@users.noreply.github.com>
aurorascharff
approved these changes
Apr 10, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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?
Adds a note to the
--debug-build-pathssection of the CLI docs clarifying that route groups must be included in file paths.Why?
When using
--debug-build-paths, users need to include route group folders (e.g.,(marketing)) in the file paths they pass. This isn't obvious from the existing documentation — route groups are stripped from URLs at runtime but must be present in file paths for this CLI option to work correctly.Addresses feedback from a docs comment noting that "Route groups are also necessary, should be inferred from file paths, but it is not straightforward from reading this."
How?
Added a "Good to know" callout with an example showing how to reference a page inside a route group:
next build --debug-build-paths="app/(marketing)/about/page.tsx"Slack Thread