codekingpro/portable-devtools

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