Skip to content

docs: clean up deprecated npm access commands #8603

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Sep 29, 2025
+5 −24
Merged

docs: clean up deprecated npm access commands #8603

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
eda195c
chore: Remove deprecated npm access commands
jsoref Sep 28, 2025
aa20a67
docs: Fix npm access references
jsoref Sep 28, 2025
655752f
docs: Undeprecate `npm access` <`grant`|`revoke`>
jsoref Sep 29, 2025
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 1 addition & 20 deletions docs/lib/content/commands/npm-access.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,29 +16,10 @@ 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.

* public / restricted (deprecated):
Set a package to be either publicly accessible or restricted.

* grant / revoke (deprecated):
Add or remove the ability of users and teams to have read-only or read-write
access to a package.

* 2fa-required / 2fa-not-required (deprecated):
Configure whether a package requires that anyone publishing it have two-factor
authentication enabled on their account.

* ls-packages (deprecated):
Show all of the packages a user or a team is able to access, along with the
access level, except for read-only public packages (it won't print the whole
registry listing)

* ls-collaborators (deprecated):
Show all of the access privileges for a package. Will only show permissions
for packages to which you have at least read access. If `<user>` is passed in,
the list is filtered only to teams _that_ user happens to belong to.

* edit (not implemented)

### Details

`npm access` always operates directly on the current registry, configurable
Expand All @@ -48,7 +29,7 @@ Unscoped packages are *always public*.

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 public` after the initial publish.
`npm access set status=public` after the initial publish.

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

Expand Down
6 changes: 3 additions & 3 deletions docs/lib/content/using-npm/orgs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,19 +71,19 @@ npm access revoke <org:team> [<package>]
* See what org packages a team member can access:

```bash
npm access ls-packages <org> <user>
npm access list packages <org> <user>
```

* See packages available to a specific team:

```bash
npm access ls-packages <org:team>
npm access list packages <org:team>
```

* Check which teams are collaborating on a package:

```bash
npm access ls-collaborators <pkg>
npm access list collaborators <pkg>
```

### See also
Expand Down
Loading