Skip to content

Commit 88c5143

Browse files
committed
chore: Unwrap markdown docs
Visual Studio Code search and replace. Search: ([a-z])\n([a-z`])(?=[a-z]) Replace: $1 $2 Flags: Case-sensitive, Regular expression Signed-off-by: Josh Soref <[email protected]>
1 parent c94b56b commit 88c5143

File tree

11 files changed

+320
-725
lines changed

11 files changed

+320
-725
lines changed

docs/lib/content/commands/npm-access.md

Lines changed: 5 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -12,24 +12,19 @@ description: Set access level on published packages
1212

1313
Used to set access controls on private packages.
1414

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

1917
* grant / revoke:
2018
Add or remove the ability of users and teams to have read-only or read-write
2119
access to a package.
2220

2321
### Details
2422

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>`.
2724

2825
Unscoped packages are *always public*.
2926

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

3429
You must have privileges to set the access of a package:
3530

@@ -38,11 +33,9 @@ You must have privileges to set the access of a package:
3833
* You have been given read-write privileges for a package, either as a member
3934
of a team or directly as an owner.
4035

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

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
4639
`--access=public`.
4740

4841
Management of teams and team memberships is done with the `npm team` command.

0 commit comments

Comments
 (0)