Gecko [ www.leshallesdegournay.geraud-market.com ]

Name	Size	Permission	Date
npm-access.md	2.47 KB	-rw-r--r--	2017-11-28 04:37
npm-adduser.md	2.68 KB	-rw-r--r--	2017-11-03 01:22
npm-bin.md	288 B	-rw-r--r--	2017-11-03 01:22
npm-bugs.md	890 B	-rw-r--r--	2017-11-03 01:22
npm-build.md	476 B	-rw-r--r--	2017-11-03 01:22
npm-bundle.md	339 B	-rw-r--r--	2016-10-13 09:50
npm-cache.md	2.56 KB	-rw-r--r--	2017-11-03 01:22
npm-completion.md	797 B	-rw-r--r--	2017-11-03 01:22
npm-config.md	1.39 KB	-rw-r--r--	2017-11-03 01:22
npm-dedupe.md	1.33 KB	-rw-r--r--	2017-11-03 01:22
npm-deprecate.md	719 B	-rw-r--r--	2017-11-03 01:22
npm-dist-tag.md	2.71 KB	-rw-r--r--	2017-11-03 01:22
npm-docs.md	989 B	-rw-r--r--	2017-11-03 01:22
npm-doctor.md	4.54 KB	-rw-r--r--	2017-11-03 01:22
npm-edit.md	850 B	-rw-r--r--	2017-11-03 01:22
npm-explore.md	869 B	-rw-r--r--	2017-11-03 01:22
npm-help-search.md	807 B	-rw-r--r--	2017-11-03 01:22
npm-help.md	816 B	-rw-r--r--	2017-11-03 01:22
npm-init.md	978 B	-rw-r--r--	2017-09-28 04:27
npm-install-test.md	705 B	-rw-r--r--	2017-11-03 01:22
npm-install.md	16.45 KB	-rw-r--r--	2017-11-28 04:37
npm-link.md	2.36 KB	-rw-r--r--	2017-11-03 01:22
npm-logout.md	1.13 KB	-rw-r--r--	2017-11-03 01:22
npm-ls.md	2.14 KB	-rw-r--r--	2017-11-03 01:22
npm-outdated.md	3.34 KB	-rw-r--r--	2017-11-03 01:22
npm-owner.md	1.08 KB	-rw-r--r--	2017-11-03 01:22
npm-pack.md	724 B	-rw-r--r--	2017-11-03 01:22
npm-ping.md	418 B	-rw-r--r--	2017-11-03 01:22
npm-prefix.md	460 B	-rw-r--r--	2017-09-28 04:27
npm-profile.md	2.82 KB	-rw-r--r--	2017-11-03 01:22
npm-prune.md	728 B	-rw-r--r--	2017-11-03 01:22
npm-publish.md	2.66 KB	-rw-r--r--	2017-11-03 01:22
npm-rebuild.md	389 B	-rw-r--r--	2017-11-03 01:22
npm-repo.md	662 B	-rw-r--r--	2017-11-03 01:22
npm-restart.md	757 B	-rw-r--r--	2017-09-28 04:27
npm-root.md	275 B	-rw-r--r--	2017-11-03 01:22
npm-run-script.md	3.08 KB	-rw-r--r--	2017-11-28 04:37
npm-search.md	2.71 KB	-rw-r--r--	2017-11-03 01:22
npm-shrinkwrap.md	690 B	-rw-r--r--	2017-11-03 01:22
npm-star.md	461 B	-rw-r--r--	2017-11-03 01:22
npm-stars.md	458 B	-rw-r--r--	2017-11-03 01:22
npm-start.md	586 B	-rw-r--r--	2017-09-28 04:27
npm-stop.md	271 B	-rw-r--r--	2017-09-28 04:27
npm-team.md	1.75 KB	-rw-r--r--	2017-11-03 01:22
npm-test.md	296 B	-rw-r--r--	2017-11-03 01:22
npm-token.md	2.74 KB	-rw-r--r--	2017-11-28 04:37
npm-uninstall.md	1.35 KB	-rw-r--r--	2017-11-03 01:22
npm-unpublish.md	1.22 KB	-rw-r--r--	2017-11-03 01:22
npm-update.md	3.34 KB	-rw-r--r--	2017-11-03 01:22
npm-version.md	4.23 KB	-rw-r--r--	2017-11-03 01:22
npm-view.md	2.93 KB	-rw-r--r--	2017-11-03 01:22
npm-whoami.md	268 B	-rw-r--r--	2017-11-03 01:22
npm.md	5.21 KB	-rw-r--r--	2017-11-03 01:22

Rename

npm-access(1) -- Set access level on published packages
=======================================================

## SYNOPSIS

npm access public [<package>]
    npm access restricted [<package>]

npm access grant <read-only|read-write> <scope:team> [<package>]
    npm access revoke <scope:team> [<package>]

npm access ls-packages [<user>|<scope>|<scope:team>]
    npm access ls-collaborators [<package> [<user>]]
    npm access edit [<package>]

## DESCRIPTION

Used to set access controls on private packages.

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:
  Set a package to be either publicly accessible or restricted.

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

* 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 won't print the whole
  registry listing)

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

* edit:
  Set the access privileges for a package at once using `$EDITOR`.

## DETAILS

`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:

* You are an owner of an unscoped or scoped package.
* You are a member of the team that owns a scope.
* You have been given read-write privileges for a package, either as a member
  of a team or directly as an owner.

If you have two-factor authentication enabled then you'll have to pass in an
otp with `--otp` when making access changes.

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.

## SEE ALSO

* npm-team(1)
* npm-publish(1)
* npm-config(7)
* npm-registry(7)