Skip to content

Snippet multi package syntax #89381

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
icyJoseph merged 3 commits into from
Feb 3, 2026
Merged

Snippet multi package syntax #89381

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4d9b7ab
docs: add multi-package manager syntax for experimental-analyze command
cursoragent Feb 2, 2026
07ef405
docs: add package manager
icyJoseph Feb 2, 2026
b80a121
Merge branch 'canary' into cursor/snippet-multi-package-syntax-5518
icyJoseph Feb 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 26 additions & 2 deletions docs/01-app/02-guides/package-bundling.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,10 +29,22 @@ The Next.js Bundle Analyzer is integrated with Turbopack's module graph. You can

To get started, run the following command and open up the interactive view in your browser.

```bash filename="Terminal"
```bash filename="Terminal" package="npm"
npx next experimental-analyze
```

```bash filename="Terminal" package="yarn"
yarn next experimental-analyze
```

```bash filename="Terminal" package="pnpm"
pnpm next experimental-analyze
```

```bash filename="Terminal" package="bun"
bunx next experimental-analyze
```

### Step 2: Filter and inspect modules

Within the UI, you can filter by route, environment (client or server), and type (JavaScript, CSS, JSON), or search by file:
Expand Down Expand Up @@ -62,10 +74,22 @@ Click a module to see its size, inspect its full import chain and see exactly wh

If you want to share the analysis with teammates or compare bundle sizes before/after optimizations, you can skip the interactive view and save the analysis as a static file with the `--output` flag:

```bash filename="Terminal"
```bash filename="Terminal" package="npm"
npx next experimental-analyze --output
```

```bash filename="Terminal" package="yarn"
yarn next experimental-analyze --output
```

```bash filename="Terminal" package="pnpm"
pnpm next experimental-analyze --output
```

```bash filename="Terminal" package="bun"
bunx next experimental-analyze --output
```

This command writes the output to `.next/diagnostics/analyze`. You can copy this directory elsewhere to compare results:

```bash filename="Terminal"
Expand Down
Loading