|o||public / restricted: Set a package to be either publicly accessible or restricted.|
|o||grant / revoke: Add or remove the ability of users and teams to have read-only or read-write access to a package.|
|o||ls-packages: 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 wont print the whole registry listing)|
|o||ls-collaborators: 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.|
Set the access privileges for a package at once using $EDITOR.
npm access always operates directly on the current registry, configurable from the command line using --registry=<registry url>.
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.
You must have privileges to set the access of a package:
o You are an owner of an unscoped or scoped package. o You are a member of the team that owns a scope. o You have been given read-write privileges for a package, either as a member of a team or directly as an owner.
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 --access=public.
Management of teams and team memberships is done with the npm team command.
o npm help team o npm help publish o npm help 7 config o npm help 7 registry
|NPM-ACCESS (1)||October 2015|