1NPM-OWNER(1)                                                      NPM-OWNER(1)
2
3
4

NAME

6       npm-owner - Manage package owners
7
8   Synopsis
9         npm owner add <user> <package-spec>
10         npm owner rm <user> <package-spec>
11         npm owner ls <package-spec>
12
13         alias: author
14
15   Description
16       Manage ownership of published packages.
17
18       •   ls: List all the users who have access to modify a package and push
19           new versions. Handy when you need to know who to bug for help.
20
21       •   add: Add a new user as a maintainer of a package. This user is  en‐
22           abled  to modify metadata, publish new versions, and add other own‐
23           ers.
24
25       •   rm: Remove a user from the package owner list. This immediately re‐
26           vokes their privileges.
27
28
29       Note  that  there  is only one level of access. Either you can modify a
30       package, or you can't. Future versions may  contain  more  fine-grained
31       access levels, but that is not implemented at this time.
32
33       If you have two-factor authentication enabled with auth-and-writes (see
34       npm help npm-profile) then you'll need to go through  a  second  factor
35       flow when changing ownership or include an otp on the command line with
36       --otp.
37
38   Configuration
39   registry
40       •   Default: "https://registry.npmjs.org/"
41
42       •   Type: URL
43
44
45       The base URL of the npm registry.
46
47   otp
48       •   Default: null
49
50       •   Type: null or String
51
52
53       This is a one-time  password  from  a  two-factor  authenticator.  It's
54       needed when publishing or changing package permissions with npm access.
55
56       If  not  set, and a registry response fails with a challenge for a one-
57       time password, npm will prompt on the command line for one.
58
59   workspace
60       •   Default:
61
62       •   Type: String (can be set multiple times)
63
64
65       Enable running a command in the context of the configured workspaces of
66       the  current project while filtering by running only the workspaces de‐
67       fined by this configuration option.
68
69       Valid values for the workspace config are either:
70
71       •   Workspace names
72
73       •   Path to a workspace directory
74
75       •   Path to a parent workspace directory (will result in selecting  all
76           workspaces within that folder)
77
78
79       When  set  for the npm init command, this may be set to the folder of a
80       workspace which does not yet exist, to create the folder and set it  up
81       as a brand new workspace within the project.
82
83       This value is not exported to the environment for child processes.
84
85   workspaces
86       •   Default: null
87
88       •   Type: null or Boolean
89
90
91       Set  to  true  to  run  the  command  in  the context of all configured
92       workspaces.
93
94       Explicitly setting this to false will cause commands  like  install  to
95       ignore workspaces altogether. When not set explicitly:
96
97       •   Commands  that  operate  on the node_modules tree (install, update,
98           etc.) will link workspaces into the node_modules folder. - Commands
99           that  do  other  things (test, exec, publish, etc.) will operate on
100           the root project, unless one or more workspaces  are  specified  in
101           the workspace config.
102
103
104       This value is not exported to the environment for child processes.
105
106   See Also
107       •   npm help "package spec"
108
109       •   npm help profile
110
111       •   npm help publish
112
113       •   npm help registry
114
115       •   npm help adduser
116
117
118
119                                 November 2023                    NPM-OWNER(1)