blob: 34917c9b88340c2f4c927d85201bdcc308edb0f9 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
.TH "NPM\-OWNER" "1" "May 2020" "" ""
.SH "NAME"
\fBnpm-owner\fR \- Manage package owners
.SS Synopsis
.P
.RS 2
.nf
npm owner add <user> [<@scope>/]<pkg>
npm owner rm <user> [<@scope>/]<pkg>
npm owner ls [<@scope>/]<pkg>
aliases: author
.fi
.RE
.SS Description
.P
Manage ownership of published packages\.
.RS 0
.IP \(bu 2
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 2
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 2
rm:
Remove a user from the package owner list\. This immediately revokes their
privileges\.
.RE
.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\fP then
you'll need to include an otp on the command line when changing ownership
with \fB\-\-otp\fP\|\.
.SS See Also
.RS 0
.IP \(bu 2
npm help publish
.IP \(bu 2
npm help registry
.IP \(bu 2
npm help adduser
.IP \(bu 2
npm help disputes
.RE
|
