diff options
Diffstat (limited to 'deps/npm/html/doc/misc/npm-scope.html')
| -rw-r--r-- | deps/npm/html/doc/misc/npm-scope.html | 23 |
1 files changed, 13 insertions, 10 deletions
diff --git a/deps/npm/html/doc/misc/npm-scope.html b/deps/npm/html/doc/misc/npm-scope.html index 21b22d926c..632ea3e24e 100644 --- a/deps/npm/html/doc/misc/npm-scope.html +++ b/deps/npm/html/doc/misc/npm-scope.html @@ -1,7 +1,7 @@ <!doctype html> <html> <title>npm-scope</title> - <meta http-equiv="content-type" value="text/html;utf-8"> + <meta charset="utf-8"> <link rel="stylesheet" type="text/css" href="../../static/style.css"> <link rel="canonical" href="https://www.npmjs.org/doc/misc/npm-scope.html"> <script async=true src="../../static/toc.js"></script> @@ -18,9 +18,10 @@ followed by a slash, e.g.</p> <pre><code>@somescope/somepackagename </code></pre><p>Scopes are a way of grouping related packages together, and also affect a few things about the way npm treats the package.</p> -<p>Scoped packages are supported by the public npm registry. The npm -client is backwards-compatible with un-scoped registries, so it can be -used to work with scoped and un-scoped registries at the same time.</p> +<p>Scoped packages can be published and installed as of <code>npm@2</code> and are supported +by the primary npm registry. The npm client is backwards-compatible with +un-scoped registries, so it can be used to work with scoped and un-scoped +registries at the same time.</p> <h2 id="installing-scoped-packages">Installing scoped packages</h2> <p>Scoped packages are installed to a sub-folder of the regular installation folder, e.g. if your other packages are installed in <code>node_modules/packagename</code>, @@ -43,11 +44,13 @@ include the name of the scope when requiring them in your code, e.g.</p> </code></pre><p>There is nothing special about the way Node treats scope folders, this is just specifying to require the module <code>mypackage</code> in the folder called <code>@myorg</code>.</p> <h2 id="publishing-scoped-packages">Publishing scoped packages</h2> -<p>Scoped packages can be published to any registry that supports them, including -the public npm registry.</p> -<p>(As of 2015-04-19, and with npm 2.0 or better, the public npm registry <strong>does</strong> support scoped packages)</p> +<p>Scoped packages can be published from the CLI as of <code>npm@2</code> and can be +published to any registry that supports them, including the primary npm +registry.</p> +<p>(As of 2015-04-19, and with npm 2.0 or better, the primary npm registry +<strong>does</strong> support scoped packages)</p> <p>If you wish, you may associate a scope with a registry; see below.</p> -<h3 id="publishing-public-scoped-packages-to-the-public-npm-registry">Publishing public scoped packages to the public npm registry</h3> +<h3 id="publishing-public-scoped-packages-to-the-primary-npm-registry">Publishing public scoped packages to the primary npm registry</h3> <p>To publish a public scoped package, you must specify <code>--access public</code> with the initial publication. This will publish the package and set access to <code>public</code> as if you had run <code>npm access public</code> after publishing.</p> @@ -61,7 +64,7 @@ restricted access. You can then change the access permissions, if desired, with <code>npm access</code> or on the npmjs.com website.</p> <h2 id="associating-a-scope-with-a-registry">Associating a scope with a registry</h2> <p>Scopes can be associated with a separate registry. This allows you to -seamlessly use a mix of packages from the public npm registry and one or more +seamlessly use a mix of packages from the primary npm registry and one or more private registries, such as npm Enterprise.</p> <p>You can associate a scope with a registry at login, e.g.</p> <pre><code>npm login --registry=http://reg.example.com --scope=@myco @@ -91,5 +94,5 @@ that registry instead.</p> <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-scope — npm@3.10.3</p> +<p id="footer">npm-scope — npm@3.10.8</p> |