[BUG] staged publish help is truncated
Open
Nobody has claimed this yet.
Bug
Needs Triage
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
This is not just a request to bump a dependency for a CVE
- This is not solely a request to bump a dependency for a CVE
Current Behavior
$ npm stage publish --help
Stage a package for publishing, deferring proof-of-presence (2FA) to a later point in time
Usage:
npm stage publish <package-spec>
Options:
[--tag <tag>] [--access <restricted|public|private>] [--dry-run] [--otp <otp>]
[-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
[--workspaces] [--include-workspace-root] [--provenance|--provenance-file <file>]
--tag
If you ask npm to install a package and don't tell it a specific version,
--access
If you do not want your scoped package to be publicly viewable (and
--dry-run
Indicates that you don't want npm to make any changes and that it should
--otp
This is a one-time password from a two-factor authenticator. It's needed
-w|--workspace
Enable running a command in the context of the configured workspaces of the
--workspaces
Set to true to run the command in the context of **all** configured
--include-workspace-root
Include the workspace root when workspaces are enabled for a command.
--provenance
When publishing from a supported cloud CI/CD system, the package will be
Expected Behavior
Help text is shown in its entirety.
Steps To Reproduce
run npm stage publish --help
Environment
- npm: 11.16.0
- Node.js: 26.3.0
- OS Name: Mac
- System Model Name: MBP
- npm config:
; "user" config from /Users/ljharb/.npmrc
//registry.npmjs.org/:_authToken = (protected)
allow-scripts = false
init-license = "MIT"
init-type = ""
init-version = "0.0.0"
; "project" config from $HOME/git/tape-testing/tape.git/.npmrc
allow-same-version = true
message = "v%s"
package-lock = false
; node bin location = $HOME/.nvm/versions/node/v26.3.0/bin/node
; node version = v26.3.0
; npm local prefix = $HOME/git/tape-testing/tape.git
; npm version = 11.16.0
; cwd = $HOME/git/tape-testing/tape.git
; HOME = $HOME
; Run `npm config ls -l` to show all defaults.
; "publishConfig" from /Users/ljharb/git/tape-testing/tape.git/package.json
; This set of config values will be used at publish-time.
ignore = [".github/workflows","types"]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running npm stage publish --help and trace the CLI help-generation entry point for the stage publish command. Compare the output with the command's complete option descriptions; done means the help text is shown in its entirety.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100