mirror of https://github.com/lukechilds/node.git
Browse Source
PR-URL: https://github.com/iojs/io.js/pull/663 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>v1.8.0-commit
Forrest L Norvell
10 years ago
committed by
Ben Noordhuis
Ben Noordhuis
202 changed files with 4155 additions and 215 deletions
@ -0,0 +1,63 @@ |
|||
npm-access(1) -- Set access level on published packages |
|||
======================================================= |
|||
|
|||
## SYNOPSIS |
|||
|
|||
npm access public [<package>] |
|||
npm access restricted [<package>] |
|||
|
|||
npm access add <read-only|read-write> <entity> [<package>] |
|||
npm access rm <entity> [<package>] |
|||
|
|||
npm access ls [<package>] |
|||
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. |
|||
|
|||
* add / rm: |
|||
Add or remove the ability of users and teams to have read-only or read-write |
|||
access to a package. |
|||
|
|||
* ls: |
|||
Show all of the access privileges for a package. Will only show permissions |
|||
for packages to which you have at least read access. |
|||
|
|||
* 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 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`. |
|||
|
|||
## SEE ALSO |
|||
|
|||
* npm-publish(1) |
|||
* npm-config(7) |
|||
* npm-registry(7) |
|||
@ -0,0 +1,72 @@ |
|||
npm-dist-tag(1) -- Modify package distribution tags |
|||
=================================================== |
|||
|
|||
## SYNOPSIS |
|||
|
|||
npm dist-tag add <pkg>@<version> [<tag>] |
|||
npm dist-tag rm <pkg> <tag> |
|||
npm dist-tag ls [<pkg>] |
|||
|
|||
## DESCRIPTION |
|||
|
|||
Add, remove, and enumerate distribution tags on a package: |
|||
|
|||
* add: |
|||
Tags the specified version of the package with the specified tag, or the |
|||
`--tag` config if not specified. |
|||
|
|||
* rm: |
|||
Clear a tag that is no longer in use from the package. |
|||
|
|||
* ls: |
|||
Show all of the dist-tags for a package, defaulting to the package in |
|||
the curren prefix. |
|||
|
|||
A tag can be used when installing packages as a reference to a version instead |
|||
of using a specific version number: |
|||
|
|||
npm install <name>@<tag> |
|||
|
|||
When installing dependencies, a preferred tagged version may be specified: |
|||
|
|||
npm install --tag <tag> |
|||
|
|||
This also applies to `npm dedupe`. |
|||
|
|||
Publishing a package always sets the "latest" tag to the published version. |
|||
|
|||
## PURPOSE |
|||
|
|||
Tags can be used to provide an alias instead of version numbers. For |
|||
example, `npm` currently uses the tag "next" to identify the upcoming |
|||
version, and the tag "latest" to identify the current version. |
|||
|
|||
A project might choose to have multiple streams of development, e.g., |
|||
"stable", "canary". |
|||
|
|||
## CAVEATS |
|||
|
|||
This command used to be known as `npm tag`, which only created new tags, and so |
|||
had a different syntax. |
|||
|
|||
Tags must share a namespace with version numbers, because they are specified in |
|||
the same slot: `npm install <pkg>@<version>` vs `npm install <pkg>@<tag>`. |
|||
|
|||
Tags that can be interpreted as valid semver ranges will be rejected. For |
|||
example, `v1.4` cannot be used as a tag, because it is interpreted by semver as |
|||
`>=1.4.0 <1.5.0`. See <https://github.com/npm/npm/issues/6082>. |
|||
|
|||
The simplest way to avoid semver problems with tags is to use tags that do not |
|||
begin with a number or the letter `v`. |
|||
|
|||
## SEE ALSO |
|||
|
|||
* npm-tag(1) |
|||
* npm-publish(1) |
|||
* npm-install(1) |
|||
* npm-dedupe(1) |
|||
* npm-registry(7) |
|||
* npm-config(1) |
|||
* npm-config(7) |
|||
* npm-tag(3) |
|||
* npmrc(5) |
|||
@ -0,0 +1,78 @@ |
|||
<!doctype html> |
|||
<html> |
|||
<title>npm-access</title> |
|||
<meta http-equiv="content-type" value="text/html;utf-8"> |
|||
<link rel="stylesheet" type="text/css" href="../../static/style.css"> |
|||
<link rel="canonical" href="https://www.npmjs.org/doc/cli/npm-access.html"> |
|||
<script async=true src="../../static/toc.js"></script> |
|||
|
|||
<body> |
|||
<div id="wrapper"> |
|||
|
|||
<h1><a href="../cli/npm-access.html">npm-access</a></h1> <p>Set access level on published packages</p> |
|||
<h2 id="synopsis">SYNOPSIS</h2> |
|||
<pre><code>npm access public [<package>] |
|||
npm access restricted [<package>] |
|||
|
|||
npm access add <read-only|read-write> <entity> [<package>] |
|||
npm access rm <entity> [<package>] |
|||
|
|||
npm access ls [<package>] |
|||
npm access edit [<package>] |
|||
</code></pre><h2 id="description">DESCRIPTION</h2> |
|||
<p>Used to set access controls on private packages.</p> |
|||
<p>For all of the subcommands, <code>npm access</code> will perform actions on the packages |
|||
in the current working directory if no package name is passed to the |
|||
subcommand.</p> |
|||
<ul> |
|||
<li><p>public / restricted: |
|||
Set a package to be either publicly accessible or restricted.</p> |
|||
</li> |
|||
<li><p>add / rm: |
|||
Add or remove the ability of users and teams to have read-only or read-write |
|||
access to a package.</p> |
|||
</li> |
|||
<li><p>ls: |
|||
Show all of the access privileges for a package. Will only show permissions |
|||
for packages to which you have at least read access.</p> |
|||
</li> |
|||
<li><p>edit: |
|||
Set the access privileges for a package at once using <code>$EDITOR</code>.</p> |
|||
</li> |
|||
</ul> |
|||
<h2 id="details">DETAILS</h2> |
|||
<p><code>npm access</code> always operates directly on the current registry, configurable |
|||
from the command line using <code>--registry=<registry url></code>.</p> |
|||
<p>Unscoped packages are <em>always public</em>.</p> |
|||
<p>Scoped packages <em>default to restricted</em>, but you can either publish them as |
|||
public using <code>npm publish --access=public</code>, or set their access as public using |
|||
<code>npm access public</code> after the initial publish.</p> |
|||
<p>You must have privileges to set the access of a package:</p> |
|||
<ul> |
|||
<li>You are an owner of an unscoped or scoped package.</li> |
|||
<li>You are a member of the team that owns a scope.</li> |
|||
<li>You have been given read-write privileges for a package, either as a member |
|||
of a team or directly as an owner.</li> |
|||
</ul> |
|||
<p>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 |
|||
<code>--access=public</code>.</p> |
|||
<h2 id="see-also">SEE ALSO</h2> |
|||
<ul> |
|||
<li><a href="../cli/npm-publish.html"><a href="../cli/npm-publish.html">npm-publish(1)</a></a></li> |
|||
<li><a href="../misc/npm-config.html"><a href="../misc/npm-config.html">npm-config(7)</a></a></li> |
|||
<li><a href="../misc/npm-registry.html"><a href="../misc/npm-registry.html">npm-registry(7)</a></a></li> |
|||
</ul> |
|||
|
|||
</div> |
|||
|
|||
<table border=0 cellspacing=0 cellpadding=0 id=npmlogo> |
|||
<tr><td style="width:180px;height:10px;background:rgb(237,127,127)" colspan=18> </td></tr> |
|||
<tr><td rowspan=4 style="width:10px;height:10px;background:rgb(237,127,127)"> </td><td style="width:40px;height:10px;background:#fff" colspan=4> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=4> </td><td style="width:40px;height:10px;background:#fff" colspan=4> </td><td rowspan=4 style="width:10px;height:10px;background:rgb(237,127,127)"> </td><td colspan=6 style="width:60px;height:10px;background:#fff"> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=4> </td></tr> |
|||
<tr><td colspan=2 style="width:20px;height:30px;background:#fff" rowspan=3> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:20px;height:10px;background:#fff" rowspan=4 colspan=2> </td><td style="width:10px;height:20px;background:rgb(237,127,127)" rowspan=2> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:20px;height:10px;background:#fff" rowspan=3 colspan=2> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td></tr> |
|||
<tr><td style="width:10px;height:10px;background:#fff" rowspan=2> </td></tr> |
|||
<tr><td style="width:10px;height:10px;background:#fff"> </td></tr> |
|||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> |
|||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> |
|||
</table> |
|||
<p id="footer">npm-access — npm@2.4.1</p> |
|||
@ -0,0 +1,79 @@ |
|||
<!doctype html> |
|||
<html> |
|||
<title>npm-dist-tag</title> |
|||
<meta http-equiv="content-type" value="text/html;utf-8"> |
|||
<link rel="stylesheet" type="text/css" href="../../static/style.css"> |
|||
<link rel="canonical" href="https://www.npmjs.org/doc/cli/npm-dist-tag.html"> |
|||
<script async=true src="../../static/toc.js"></script> |
|||
|
|||
<body> |
|||
<div id="wrapper"> |
|||
|
|||
<h1><a href="../cli/npm-dist-tag.html">npm-dist-tag</a></h1> <p>Modify package distribution tags</p> |
|||
<h2 id="synopsis">SYNOPSIS</h2> |
|||
<pre><code>npm dist-tag add <pkg>@<version> [<tag>] |
|||
npm dist-tag rm <pkg> <tag> |
|||
npm dist-tag ls [<pkg>] |
|||
</code></pre><h2 id="description">DESCRIPTION</h2> |
|||
<p>Add, remove, and enumerate distribution tags on a package:</p> |
|||
<ul> |
|||
<li><p>add: |
|||
Tags the specified version of the package with the specified tag, or the |
|||
<code>--tag</code> config if not specified.</p> |
|||
</li> |
|||
<li><p>rm: |
|||
Clear a tag that is no longer in use from the package.</p> |
|||
</li> |
|||
<li><p>ls: |
|||
Show all of the dist-tags for a package, defaulting to the package in |
|||
the curren prefix.</p> |
|||
</li> |
|||
</ul> |
|||
<p>A tag can be used when installing packages as a reference to a version instead |
|||
of using a specific version number:</p> |
|||
<pre><code>npm install <name>@<tag> |
|||
</code></pre><p>When installing dependencies, a preferred tagged version may be specified:</p> |
|||
<pre><code>npm install --tag <tag> |
|||
</code></pre><p>This also applies to <code>npm dedupe</code>.</p> |
|||
<p>Publishing a package always sets the "latest" tag to the published version.</p> |
|||
<h2 id="purpose">PURPOSE</h2> |
|||
<p>Tags can be used to provide an alias instead of version numbers. For |
|||
example, <code>npm</code> currently uses the tag "next" to identify the upcoming |
|||
version, and the tag "latest" to identify the current version.</p> |
|||
<p>A project might choose to have multiple streams of development, e.g., |
|||
"stable", "canary".</p> |
|||
<h2 id="caveats">CAVEATS</h2> |
|||
<p>This command used to be known as <code>npm tag</code>, which only created new tags, and so |
|||
had a different syntax.</p> |
|||
<p>Tags must share a namespace with version numbers, because they are specified in |
|||
the same slot: <code>npm install <pkg>@<version></code> vs <code>npm install <pkg>@<tag></code>.</p> |
|||
<p>Tags that can be interpreted as valid semver ranges will be rejected. For |
|||
example, <code>v1.4</code> cannot be used as a tag, because it is interpreted by semver as |
|||
<code>>=1.4.0 <1.5.0</code>. See <a href="https://github.com/npm/npm/issues/6082">https://github.com/npm/npm/issues/6082</a>.</p> |
|||
<p>The simplest way to avoid semver problems with tags is to use tags that do not |
|||
begin with a number or the letter <code>v</code>.</p> |
|||
<h2 id="see-also">SEE ALSO</h2> |
|||
<ul> |
|||
<li><a href="../cli/npm-tag.html"><a href="../cli/npm-tag.html">npm-tag(1)</a></a></li> |
|||
<li><a href="../cli/npm-publish.html"><a href="../cli/npm-publish.html">npm-publish(1)</a></a></li> |
|||
<li><a href="../cli/npm-install.html"><a href="../cli/npm-install.html">npm-install(1)</a></a></li> |
|||
<li><a href="../cli/npm-dedupe.html"><a href="../cli/npm-dedupe.html">npm-dedupe(1)</a></a></li> |
|||
<li><a href="../misc/npm-registry.html"><a href="../misc/npm-registry.html">npm-registry(7)</a></a></li> |
|||
<li><a href="../cli/npm-config.html"><a href="../cli/npm-config.html">npm-config(1)</a></a></li> |
|||
<li><a href="../misc/npm-config.html"><a href="../misc/npm-config.html">npm-config(7)</a></a></li> |
|||
<li><a href="../api/npm-tag.html"><a href="../api/npm-tag.html">npm-tag(3)</a></a></li> |
|||
<li><a href="../files/npmrc.html"><a href="../files/npmrc.html">npmrc(5)</a></a></li> |
|||
</ul> |
|||
|
|||
</div> |
|||
|
|||
<table border=0 cellspacing=0 cellpadding=0 id=npmlogo> |
|||
<tr><td style="width:180px;height:10px;background:rgb(237,127,127)" colspan=18> </td></tr> |
|||
<tr><td rowspan=4 style="width:10px;height:10px;background:rgb(237,127,127)"> </td><td style="width:40px;height:10px;background:#fff" colspan=4> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=4> </td><td style="width:40px;height:10px;background:#fff" colspan=4> </td><td rowspan=4 style="width:10px;height:10px;background:rgb(237,127,127)"> </td><td colspan=6 style="width:60px;height:10px;background:#fff"> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=4> </td></tr> |
|||
<tr><td colspan=2 style="width:20px;height:30px;background:#fff" rowspan=3> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:20px;height:10px;background:#fff" rowspan=4 colspan=2> </td><td style="width:10px;height:20px;background:rgb(237,127,127)" rowspan=2> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:20px;height:10px;background:#fff" rowspan=3 colspan=2> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td></tr> |
|||
<tr><td style="width:10px;height:10px;background:#fff" rowspan=2> </td></tr> |
|||
<tr><td style="width:10px;height:10px;background:#fff"> </td></tr> |
|||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> |
|||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> |
|||
</table> |
|||
<p id="footer">npm-dist-tag — npm@2.4.1</p> |
|||
Some files were not shown because too many files changed in this diff
Loading…
Reference in new issue