- Notifications
You must be signed in to change notification settings - Fork30.1k
docs: next experimental-analyze#87272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:canary
Are you sure you want to change the base?
Conversation
Hi there 👋 It looks like this PR introduces broken links to the docs, please take a moment to fix them before merging:
Thank you 🙏 |
| - View the full import chain showing why a module is included | ||
| - Trace imports across server-to-client component boundaries and dynamic imports | ||
| See[Package Bundling](/docs/app/guides/package-bundling#turbopack-bundle-analyzer-experimental) for optimization strategies. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
| See[Package Bundling](/docs/app/guides/package-bundling#turbopack-bundle-analyzer-experimental) for optimization strategies. | |
| See[Package Bundling](/docs/app/guides/package-bundling) for optimization strategies. |
The documentation links to a non-existent section anchor in the package-bundling guide. The anchor#turbopack-bundle-analyzer-experimental doesn't exist in/docs/app/guides/package-bundling.mdx.
View Details
Analysis
Broken documentation link with non-existent anchor in CLI reference
What fails: Line 218 indocs/01-app/03-api-reference/06-cli/next.mdx contains a link to#turbopack-bundle-analyzer-experimental anchor that does not exist in the target documentdocs/01-app/02-guides/package-bundling.mdx.
How to reproduce: Opendocs/01-app/03-api-reference/06-cli/next.mdx line 218 and click on the "Package Bundling" link with the anchor#turbopack-bundle-analyzer-experimental.
Result: Users are directed to the top of the package-bundling page instead of a specific relevant section.
Expected: The link should resolve to an actual section heading in the package-bundling guide or point to the main page without the anchor.
Fix applied: Removed the non-existent anchor#turbopack-bundle-analyzer-experimental and linked to the main package-bundling page at/docs/app/guides/package-bundling. The "Analyzing JavaScript bundles" section in the target document is the most relevant content for thenext experimental-analyze command documentation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Adding CLI docs for next experimental-analyze