Go to main content

man pages section 1: User Commands

Exit Print View

Updated: Wednesday, July 27, 2022
 
 

npm-owner (1)

Name

npm-owner - Manage package owners Synopsis npm owner add <user> [<@scope>/]<pkg> npm owner rm <user> [<@scope>/]<pkg> npm owner ls [<@scope>/]<pkg> alias: author Note: This command is unaware of workspaces. Description Manage ownership of published packages. o 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. o add: Add a new user as a maintainer of a package. This user is enabled to modify metadata, publish new versions, and add other own- ers. o 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 (see npm help npm-profile) then you'll need to include an otp on the command line when changing ownership with --otp. Configuration registry o Default: "https://registry.npmjs.org/" o Type: URL The base URL of the npm registry. otp o Default: null o Type: null or String This is a one-time password from a two-factor authenticator. It's needed when publishing or changing package permissions with npm access. 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. See Also o npm help profile o npm help publish o npm help registry o npm help adduser

Synopsis

Please see following description for synopsis

Description

NPM-OWNER(1)                                                      NPM-OWNER(1)



NAME
       npm-owner - Manage package owners

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

         alias: author

       Note: This command is unaware of workspaces.

   Description
       Manage ownership of published packages.

       o 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.

       o add: Add a new user as a maintainer  of  a  package.   This  user  is
         enabled  to modify metadata, publish new versions, and add other own-
         ers.

       o 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 (see
       npm help npm-profile) then you'll need to include an otp on the command
       line when changing ownership with --otp.

   Configuration
   registry
       o Default: "https://registry.npmjs.org/"

       o Type: URL


       The base URL of the npm registry.

   otp
       o Default: null

       o Type: null or String


       This  is  a  one-time  password  from  a two-factor authenticator. It's
       needed when publishing or changing package permissions with npm access.

       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.

   See Also
       o npm help profile

       o npm help publish

       o npm help registry

       o npm help adduser




ATTRIBUTES
       See attributes(7) for descriptions of the following attributes:


       +---------------+--------------------------+
       |ATTRIBUTE TYPE |     ATTRIBUTE VALUE      |
       +---------------+--------------------------+
       |Availability   | runtime/nodejs/nodejs-18 |
       +---------------+--------------------------+
       |Stability      | Pass-thru volatile       |
       +---------------+--------------------------+

NOTES
       Source  code  for open source software components in Oracle Solaris can
       be found at https://www.oracle.com/downloads/opensource/solaris-source-
       code-downloads.html.

       This     software     was    built    from    source    available    at
       https://github.com/oracle/solaris-userland.   The  original   community
       source    was   downloaded   from    https://github.com/nodejs/node/ar-
       chive/v18.1.0.zip.

       Further information about this software can be found on the open source
       community website at https://github.com/nodejs/node.



                                  April 2022                      NPM-OWNER(1)