mirrors/nodejs
mirrors/nodejs
0
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-12-01 16:10:02 +01:00
Code Issues Releases Activity
5842366ae8
nodejs/deps/npm/doc/cli/npm-owner.md
Myles Borins ace4fe566f
deps: update npm to 5.5.1 
Closes: https://github.com/nodejs/node/pull/16280

PR-URL: https://github.com/nodejs/node/pull/16509
Fixes: https://github.com/nodejs/node/issues/14161
Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
2017-10-29 21:32:15 -04:00

1.1 KiB
Raw Blame History

npm-owner(1) -- Manage package owners

SYNOPSIS

npm owner add <user> [<@scope>/]<pkg>
npm owner rm <user> [<@scope>/]<pkg>
npm owner ls [<@scope>/]<pkg>

aliases: author

DESCRIPTION

Manage ownership of published packages.

  • 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.
  • 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.
  • rm: Remove a user from the package owner list. This immediately revokes their privileges.

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.

If you have two-factor authentication enabled with auth-and-writes then you'll need to include an otp on the command line when changing ownership with --otp.

SEE ALSO

  • npm-publish(1)
  • npm-registry(7)
  • npm-adduser(1)
  • npm-disputes(7)