You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/lib/content/commands/npm-access.md
+5-12Lines changed: 5 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,24 +12,19 @@ description: Set access level on published packages
12
12
13
13
Used to set access controls on private packages.
14
14
15
-
For all of the subcommands, `npm access` will perform actions on the packages
16
-
in the current working directory if no package name is passed to the
17
-
subcommand.
15
+
For all of the subcommands, `npm access` will perform actions on the packages in the current working directory if no package name is passed to the subcommand.
18
16
19
17
* grant / revoke:
20
18
Add or remove the ability of users and teams to have read-only or read-write
21
19
access to a package.
22
20
23
21
### Details
24
22
25
-
`npm access` always operates directly on the current registry, configurable
26
-
from the command line using `--registry=<registry url>`.
23
+
`npm access` always operates directly on the current registry, configurable from the command line using `--registry=<registry url>`.
27
24
28
25
Unscoped packages are *always public*.
29
26
30
-
Scoped packages *default to restricted*, but you can either publish them as
31
-
public using `npm publish --access=public`, or set their access as public using
32
-
`npm access set status=public` after the initial publish.
27
+
Scoped packages *default to restricted*, but you can either publish them as public using `npm publish --access=public`, or set their access as public using `npm access set status=public` after the initial publish.
33
28
34
29
You must have privileges to set the access of a package:
35
30
@@ -38,11 +33,9 @@ You must have privileges to set the access of a package:
38
33
* You have been given read-write privileges for a package, either as a member
39
34
of a team or directly as an owner.
40
35
41
-
If you have two-factor authentication enabled then you'll be prompted to provide a second factor, or may use the `--otp=...` option to specify it on
42
-
the command line.
36
+
If you have two-factor authentication enabled then you'll be prompted to provide a second factor, or may use the `--otp=...` option to specify it on the command line.
43
37
44
-
If your account is not paid, then attempts to publish scoped packages will
45
-
fail with an HTTP 402 status code (logically enough), unless you use
38
+
If your account is not paid, then attempts to publish scoped packages will fail with an HTTP 402 status code (logically enough), unless you use
46
39
`--access=public`.
47
40
48
41
Management of teams and team memberships is done with the `npm team` command.
0 commit comments