/snap/node/11691/lib/node_modules/npm/man/man1/
/snap/node/11691/lib/node_modules/npm/man/man1
NameSizeModeActions
npm-access.140630644editdlrm
npm-adduser.119930644editdlrm
npm-audit.1173820644editdlrm
npm-bugs.133800644editdlrm
npm-cache.131330644editdlrm
npm-ci.1101820644editdlrm
npm-completion.19980644editdlrm
npm-config.146370644editdlrm
npm-dedupe.198630644editdlrm
npm-deprecate.118930644editdlrm
npm-diff.197720644editdlrm
npm-dist-tag.156370644editdlrm
npm-docs.133620644editdlrm
npm-doctor.153730644editdlrm
npm-edit.111810644editdlrm
npm-exec.1124920644editdlrm
npm-explain.129380644editdlrm
npm-explore.110900644editdlrm
npm-find-dupes.175910644editdlrm
npm-fund.140550644editdlrm
npm-help-search.18680644editdlrm
npm-help.111000644editdlrm
npm-hook.127090644editdlrm
npm-init.1111110644editdlrm
npm-install-ci-test.183210644editdlrm
npm-install-test.1111500644editdlrm
npm-install.1267720644editdlrm
npm-link.1129510644editdlrm
npm-login.123460644editdlrm
npm-logout.118880644editdlrm
npm-ls.194200644editdlrm
npm-org.123110644editdlrm
npm-outdated.163780644editdlrm
npm-owner.133640644editdlrm
npm-pack.138770644editdlrm
npm-ping.18500644editdlrm
npm-pkg.187050644editdlrm
npm-prefix.113180644editdlrm
npm-profile.134220644editdlrm
npm-prune.164580644editdlrm
npm-publish.183100644editdlrm
npm-query.176890644editdlrm
npm-rebuild.156650644editdlrm
npm-repo.131440644editdlrm
npm-restart.117100644editdlrm
npm-root.111950644editdlrm
npm-run-script.183780644editdlrm
npm-sbom.189970644editdlrm
npm-search.139530644editdlrm
npm-shrinkwrap.110050644editdlrm
npm-star.118080644editdlrm
npm-stars.17960644editdlrm
npm-start.118360644editdlrm
npm-stop.114670644editdlrm
npm-team.145040644editdlrm
npm-test.113800644editdlrm
npm-token.131870644editdlrm
npm-uninstall.149870644editdlrm
npm-unpublish.149010644editdlrm
npm-unstar.116590644editdlrm
npm-update.1132240644editdlrm
npm-version.177560644editdlrm
npm-view.161470644editdlrm
npm-whoami.18740644editdlrm
npm.159480644editdlrm
npx.164080644editdlrm
Edit: /snap/node/11691/lib/node_modules/npm/man/man1/npm-owner.1 (3364B)
.TH "NPM-OWNER" "1" "March 2026" "NPM@10.9.8" "" .SH "NAME" \fBnpm-owner\fR - Manage package owners .SS "Synopsis" .P .RS 2 .nf npm owner add npm owner rm npm owner ls alias: author .fi .RE .SS "Description" .P Manage ownership of published packages. .RS 0 .IP \(bu 4 ls: List all the users who have access to modify a package and push new versions. Handy when you need to know who to bug for help. .IP \(bu 4 add: Add a new user as a maintainer of a package. This user is enabled to modify metadata, publish new versions, and add other owners. .IP \(bu 4 rm: Remove a user from the package owner list. This immediately revokes their privileges. .RE 0 .P Note that there is only one level of access. Either you can modify a package, or you can't. Future versions may contain more fine-grained access levels, but that is not implemented at this time. .P If you have two-factor authentication enabled with \fBauth-and-writes\fR (see npm help npm-profile) then you'll need to go through a second factor flow when changing ownership or include an otp on the command line with \fB--otp\fR. .SS "Configuration" .SS "\fBregistry\fR" .RS 0 .IP \(bu 4 Default: "https://registry.npmjs.org/" .IP \(bu 4 Type: URL .RE 0 .P The base URL of the npm registry. .SS "\fBotp\fR" .RS 0 .IP \(bu 4 Default: null .IP \(bu 4 Type: null or String .RE 0 .P This is a one-time password from a two-factor authenticator. It's needed when publishing or changing package permissions with \fBnpm access\fR. .P If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one. .SS "\fBworkspace\fR" .RS 0 .IP \(bu 4 Default: .IP \(bu 4 Type: String (can be set multiple times) .RE 0 .P Enable running a command in the context of the configured workspaces of the current project while filtering by running only the workspaces defined by this configuration option. .P Valid values for the \fBworkspace\fR config are either: .RS 0 .IP \(bu 4 Workspace names .IP \(bu 4 Path to a workspace directory .IP \(bu 4 Path to a parent workspace directory (will result in selecting all workspaces within that folder) .RE 0 .P When set for the \fBnpm init\fR command, this may be set to the folder of a workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project. .P This value is not exported to the environment for child processes. .SS "\fBworkspaces\fR" .RS 0 .IP \(bu 4 Default: null .IP \(bu 4 Type: null or Boolean .RE 0 .P Set to true to run the command in the context of \fBall\fR configured workspaces. .P Explicitly setting this to false will cause commands like \fBinstall\fR to ignore workspaces altogether. When not set explicitly: .RS 0 .IP \(bu 4 Commands that operate on the \fBnode_modules\fR tree (install, update, etc.) will link workspaces into the \fBnode_modules\fR folder. - Commands that do other things (test, exec, publish, etc.) will operate on the root project, \fIunless\fR one or more workspaces are specified in the \fBworkspace\fR config. .RE 0 .P This value is not exported to the environment for child processes. .SS "See Also" .RS 0 .IP \(bu 4 npm help "package spec" .IP \(bu 4 npm help profile .IP \(bu 4 npm help publish .IP \(bu 4 npm help registry .IP \(bu 4 npm help adduser .RE 0