/
snap
/
node
/
11691
/
lib
/
node_modules
/
npm
/
man
/
man1
/
/snap/node/11691/lib/node_modules/npm/man/man1
mkdir
upload
Name
Size
Mode
Actions
npm-access.1
4063
0644
edit
dl
rm
npm-adduser.1
1993
0644
edit
dl
rm
npm-audit.1
17382
0644
edit
dl
rm
npm-bugs.1
3380
0644
edit
dl
rm
npm-cache.1
3133
0644
edit
dl
rm
npm-ci.1
10182
0644
edit
dl
rm
npm-completion.1
998
0644
edit
dl
rm
npm-config.1
4637
0644
edit
dl
rm
npm-dedupe.1
9863
0644
edit
dl
rm
npm-deprecate.1
1893
0644
edit
dl
rm
npm-diff.1
9772
0644
edit
dl
rm
npm-dist-tag.1
5637
0644
edit
dl
rm
npm-docs.1
3362
0644
edit
dl
rm
npm-doctor.1
5373
0644
edit
dl
rm
npm-edit.1
1181
0644
edit
dl
rm
npm-exec.1
12492
0644
edit
dl
rm
npm-explain.1
2938
0644
edit
dl
rm
npm-explore.1
1090
0644
edit
dl
rm
npm-find-dupes.1
7591
0644
edit
dl
rm
npm-fund.1
4055
0644
edit
dl
rm
npm-help-search.1
868
0644
edit
dl
rm
npm-help.1
1100
0644
edit
dl
rm
npm-hook.1
2709
0644
edit
dl
rm
npm-init.1
11111
0644
edit
dl
rm
npm-install-ci-test.1
8321
0644
edit
dl
rm
npm-install-test.1
11150
0644
edit
dl
rm
npm-install.1
26772
0644
edit
dl
rm
npm-link.1
12951
0644
edit
dl
rm
npm-login.1
2346
0644
edit
dl
rm
npm-logout.1
1888
0644
edit
dl
rm
npm-ls.1
9420
0644
edit
dl
rm
npm-org.1
2311
0644
edit
dl
rm
npm-outdated.1
6378
0644
edit
dl
rm
npm-owner.1
3364
0644
edit
dl
rm
npm-pack.1
3877
0644
edit
dl
rm
npm-ping.1
850
0644
edit
dl
rm
npm-pkg.1
8705
0644
edit
dl
rm
npm-prefix.1
1318
0644
edit
dl
rm
npm-profile.1
3422
0644
edit
dl
rm
npm-prune.1
6458
0644
edit
dl
rm
npm-publish.1
8310
0644
edit
dl
rm
npm-query.1
7689
0644
edit
dl
rm
npm-rebuild.1
5665
0644
edit
dl
rm
npm-repo.1
3144
0644
edit
dl
rm
npm-restart.1
1710
0644
edit
dl
rm
npm-root.1
1195
0644
edit
dl
rm
npm-run-script.1
8378
0644
edit
dl
rm
npm-sbom.1
8997
0644
edit
dl
rm
npm-search.1
3953
0644
edit
dl
rm
npm-shrinkwrap.1
1005
0644
edit
dl
rm
npm-star.1
1808
0644
edit
dl
rm
npm-stars.1
796
0644
edit
dl
rm
npm-start.1
1836
0644
edit
dl
rm
npm-stop.1
1467
0644
edit
dl
rm
npm-team.1
4504
0644
edit
dl
rm
npm-test.1
1380
0644
edit
dl
rm
npm-token.1
3187
0644
edit
dl
rm
npm-uninstall.1
4987
0644
edit
dl
rm
npm-unpublish.1
4901
0644
edit
dl
rm
npm-unstar.1
1659
0644
edit
dl
rm
npm-update.1
13224
0644
edit
dl
rm
npm-version.1
7756
0644
edit
dl
rm
npm-view.1
6147
0644
edit
dl
rm
npm-whoami.1
874
0644
edit
dl
rm
npm.1
5948
0644
edit
dl
rm
npx.1
6408
0644
edit
dl
rm
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 <user> <package-spec> npm owner rm <user> <package-spec> npm owner ls <package-spec> 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
Save
cmd:
run