/home/techb158/.nvm/versions/node/v22.6.0/lib/node_modules/npm/man/man1
NameSizeModeActions
npm-access.140620644editdlrm
npm-adduser.119920644editdlrm
npm-audit.1173810644editdlrm
npm-bugs.133790644editdlrm
npm-cache.131320644editdlrm
npm-ci.1101810644editdlrm
npm-completion.19970644editdlrm
npm-config.146360644editdlrm
npm-dedupe.198620644editdlrm
npm-deprecate.118920644editdlrm
npm-diff.197710644editdlrm
npm-dist-tag.156360644editdlrm
npm-docs.133610644editdlrm
npm-doctor.153720644editdlrm
npm-edit.111800644editdlrm
npm-exec.1124910644editdlrm
npm-explain.129370644editdlrm
npm-explore.110890644editdlrm
npm-find-dupes.175900644editdlrm
npm-fund.140540644editdlrm
npm-help-search.18670644editdlrm
npm-help.110990644editdlrm
npm-hook.127080644editdlrm
npm-init.1111030644editdlrm
npm-install-ci-test.183200644editdlrm
npm-install-test.1111490644editdlrm
npm-install.1269640644editdlrm
npm-link.1129500644editdlrm
npm-login.123450644editdlrm
npm-logout.118870644editdlrm
npm-ls.194190644editdlrm
npm-org.123100644editdlrm
npm-outdated.163770644editdlrm
npm-owner.133630644editdlrm
npm-pack.138760644editdlrm
npm-ping.18490644editdlrm
npm-pkg.187040644editdlrm
npm-prefix.113170644editdlrm
npm-profile.134210644editdlrm
npm-prune.164570644editdlrm
npm-publish.183090644editdlrm
npm-query.176880644editdlrm
npm-rebuild.156640644editdlrm
npm-repo.131430644editdlrm
npm-restart.117090644editdlrm
npm-root.111940644editdlrm
npm-run-script.183770644editdlrm
npm-sbom.189960644editdlrm
npm-search.139520644editdlrm
npm-shrinkwrap.110040644editdlrm
npm-star.118070644editdlrm
npm-stars.17950644editdlrm
npm-start.118350644editdlrm
npm-stop.114660644editdlrm
npm-team.145030644editdlrm
npm-test.113790644editdlrm
npm-token.131860644editdlrm
npm-uninstall.149860644editdlrm
npm-unpublish.149000644editdlrm
npm-unstar.116580644editdlrm
npm-update.1132230644editdlrm
npm-version.177550644editdlrm
npm-view.161460644editdlrm
npm-whoami.18730644editdlrm
npm.159470644editdlrm
npx.164070644editdlrm
Edit: /home/techb158/.nvm/versions/node/v22.6.0/lib/node_modules/npm/man/man1/npm-owner.1 (3363B)
.TH "NPM-OWNER" "1" "July 2024" "NPM@10.8.2" "" .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