Guide: Update Optimizing Package Bundling to include Turbopack Bundle Analyzer
#87246
+53
−12
Conversation
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
nextjs-bot
added
created-by: Next.js DevEx team
Contributor
|
All broken links are now fixed, thank you! |
delbaoliveira
changed the title
Optimizing Package Bundling to include Turbopack Bundle Analyzer
icyJoseph
reviewed
Dec 16, 2025
delbaoliveira
commented
Dec 16, 2025
| --- | ||
|
|
||
| Bundling external packages can significantly improve the performance of your application. <AppOnly>By default, packages imported inside Server Components and Route Handlers are automatically bundled by Next.js. This page will guide you through how to analyze and further optimize package bundling.</AppOnly> <PagesOnly>By default, packages imported into your application are not bundled. This can impact performance or might not work if external packages are not pre-bundled, for example, if imported from a monorepo or `node_modules`. This page will guide you through how to analyze and configure package bundling.</PagesOnly> | ||
| Large bundles can negatively impact your application's performance. <AppOnly>By default, Next.js automatically bundles packages imported inside Server Components and Route Handlers.</AppOnly><PagesOnly>By default, packages imported into your application are not bundled, which can be a source of performance issues if external packages are not pre-bundled, for example, if imported from a monorepo or `node_modules`.</PagesOnly>. In some cases, you may need to further optimize it. |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| Large bundles can negatively impact your application's performance. <AppOnly>By default, Next.js automatically bundles packages imported inside Server Components and Route Handlers.</AppOnly><PagesOnly>By default, packages imported into your application are not bundled, which can be a source of performance issues if external packages are not pre-bundled, for example, if imported from a monorepo or `node_modules`.</PagesOnly>. In some cases, you may need to further optimize it. | |
| Large bundles can negatively impact your application's performance. <AppOnly>By default, Next.js automatically bundles packages imported inside Server Components and Route Handlers.</AppOnly><PagesOnly>By default, packages imported into your application are not bundled, which can be a source of performance issues if external packages are not pre-bundled, for example, if imported from a monorepo or `node_modules`.</PagesOnly>. In some cases, you may need to further optimize client bundles. |
| To get started, run the following command and open up the interactive view in your browser. | ||
|
|
||
| ```bash | ||
| npx next experimental-analyze --serve |
Contributor
There was a problem hiding this comment.
we are going to drop the --serve flag
Member
There was a problem hiding this comment.
Suggested change
| npx next experimental-analyze --serve | |
| npx next experimental-analyze |
| @@ -1,20 +1,61 @@ | |||
| --- | |||
| title: How to optimize package bundling | |||
| title: Optmizing package bundling | |||
Contributor
There was a problem hiding this comment.
Suggested change
| title: Optmizing package bundling | |
| title: Optimizing package bundling |
|
|
||
| ## Turbopack Bundle Analyzer (Experimental) | ||
|
|
||
| > This experimental feature is available in v16.1 and above. You can share feedback on the [dedicated GitHub discussion](https://github.com/vercel/next.js/discussions/86731). |
Contributor
There was a problem hiding this comment.
I am hosting a demo here: https://turbopack-bundle-analyzer-demo.vercel.sh/
we plan on keeping it roughly up to date, and will be linking from the blog post.
lukesandberg
approved these changes
Dec 18, 2025
Sign up for free
to 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.
This PR adds instructions on how to run and navigate the new turbopack bundle analyzer to the existing Optimizing package bundling guide
.
Todo: