Skip to content

docs: update npm stage docs to reflect that it can create new packages #10050

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
reggi merged 1 commit into from
Sep 29, 2026
+1 −2
Merged

docs: update npm stage docs to reflect that it can create new packages #10050

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 1 addition & 2 deletions docs/lib/content/commands/npm-stage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,7 @@ Key behaviors:
version for that package.
* You can still publish packages normally while you have staged packages
pending.
* Staged publishing will allow you to create a new package if it does not exist.
* You can stage multiple versions of the same package.
* `npm stage publish` has parity with `npm publish` and will respect
`"private": true` in `package.json`, refusing to stage the package.
Expand All @@ -46,8 +47,6 @@ Before using `npm stage` commands, ensure the following requirements are met:

* **Write permissions on the package:** You must have write access to the
package you're configuring.
* **Package must exist:** The package you're configuring must already exist
on the npm registry.
* **2FA enabled on your account:** Commands that require 2FA will prompt you
to authenticate. If you don't already have 2FA enabled on your account,
you must enable it before using these commands.
Expand Down
Loading