Skip to content

Snippet multi package syntax#89381

Merged
icyJoseph merged 3 commits intocanaryfrom
cursor/snippet-multi-package-syntax-5518
Feb 3, 2026
Merged

Snippet multi package syntax#89381
icyJoseph merged 3 commits intocanaryfrom
cursor/snippet-multi-package-syntax-5518

Conversation

@icyJoseph
Copy link
Collaborator

Add yarn and pnpm alternatives alongside npx for running the
experimental-analyze command. This helps avoid confusion where users
might use pnpx (which downloads from registry) instead of pnpm
(which uses local node_modules).

Co-authored-by: joseph.chamochumbi <joseph.chamochumbi@vercel.com>
@cursor
Copy link

cursor bot commented Feb 2, 2026

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

@nextjs-bot nextjs-bot added created-by: Next.js DevEx team PRs by the DX team. Documentation Related to Next.js' official documentation. labels Feb 2, 2026
@icyJoseph icyJoseph marked this pull request as ready for review February 3, 2026 00:48
@icyJoseph icyJoseph merged commit 7437fed into canary Feb 3, 2026
72 checks passed
@icyJoseph icyJoseph deleted the cursor/snippet-multi-package-syntax-5518 branch February 3, 2026 00:56
bgub pushed a commit to bgub/next.js that referenced this pull request Feb 5, 2026
<!-- 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>

---------

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

created-by: Next.js DevEx team PRs by the DX team. Documentation Related to Next.js' official documentation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants