Repository: vercel/next.js
Pull request: Snippet multi package syntax

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the PR.
- Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to understand the PR)
- When linking to a Slack thread, you might want to share details of the conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic behind a change

### What?
Updated `docs/01-app/02-guides/package-bundling.mdx` to use multi-package manager syntax for `next experimental-analyze` commands.

### Why?
To clarify the correct way to run `next experimental-analyze` with different package managers (npx, yarn, pnpm), preventing common mistakes like using `pnpx` instead of `pnpm next` for local binary execution.

### How?
Added `yarn next experimental-analyze` and `pnpm next experimental-analyze` alternatives to the `npx next experimental-analyze` code blocks in Step 1 and Step 4.

Closes NEXT-
Fixes #

-->

---
[Slack Thread](https://vercel.slack.com/archives/C046HAU4H7F/p1770024460553639?thread_ts=1770024460.553639&cid=C046HAU4H7F)

<a href="https://cursor.com/background-agent?bcId=bc-9b5e5ceb-78cf-5495-953e-53c04d01399c"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;<a href="https://cursor.com/agents?id=bc-9b5e5ceb-78cf-5495-953e-53c04d01399c"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>



Changed files:
filename: docs/01-app/02-guides/package-bundling.mdx
patch: @@ -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:
@@ -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"