diff options
Diffstat (limited to 'deps/npm/html/doc/misc/npm-faq.html')
| -rw-r--r-- | deps/npm/html/doc/misc/npm-faq.html | 47 |
1 files changed, 35 insertions, 12 deletions
diff --git a/deps/npm/html/doc/misc/npm-faq.html b/deps/npm/html/doc/misc/npm-faq.html index 08c8eafce2..6caf41929f 100644 --- a/deps/npm/html/doc/misc/npm-faq.html +++ b/deps/npm/html/doc/misc/npm-faq.html @@ -11,7 +11,7 @@ <h1><a href="../misc/npm-faq.html">npm-faq</a></h1> <p>Frequently Asked Questions</p> <h2 id="where-can-i-find-these-docs-in-html-">Where can I find these docs in HTML?</h2> -<p><a href="https://www.npmjs.org/doc/">https://www.npmjs.org/doc/</a>, or run:</p> +<p><a href="https://docs.npmjs.com/">https://docs.npmjs.com/</a>, or run:</p> <pre><code>npm config set viewer browser </code></pre><p>to open these documents in your default web browser rather than <code>man</code>.</p> <h2 id="it-didn-t-work-">It didn't work.</h2> @@ -62,7 +62,7 @@ in a shell script if you really wanted to.</p> <p>Usually, no. Allow npm to resolve dependencies for your packages.</p> <p>For packages you <strong>deploy</strong>, such as websites and apps, you should use npm shrinkwrap to lock down your full dependency tree:</p> -<p><a href="https://www.npmjs.org/doc/cli/npm-shrinkwrap.html">https://www.npmjs.org/doc/cli/npm-shrinkwrap.html</a></p> +<p><a href="https://docs.npmjs.com/cli/shrinkwrap">https://docs.npmjs.com/cli/shrinkwrap</a></p> <p>If you are paranoid about depending on the npm ecosystem, you should run a private npm mirror or a private cache.</p> <p>If you want 100% confidence in being able to reproduce the specific bytes @@ -108,7 +108,7 @@ version cannot be properly installed with the version that you have installed already. (Consider, if there is ever a bug in the <code>update</code> command.)</p> <p>In those cases, you can do this:</p> -<pre><code>curl https://www.npmjs.org/install.sh | sh +<pre><code>curl https://www.npmjs.com/install.sh | sh </code></pre><h2 id="what-is-a-package-">What is a <code>package</code>?</h2> <p>A package is:</p> <ul> @@ -230,28 +230,51 @@ that has a package.json in its root, or a git url. <h2 id="the-package-registry-website-what-is-that-exactly-">The package registry website. What is that exactly?</h2> <p>See <code><a href="../misc/npm-registry.html"><a href="../misc/npm-registry.html">npm-registry(7)</a></a></code>.</p> <h2 id="i-forgot-my-password-and-can-t-publish-how-do-i-reset-it-">I forgot my password, and can't publish. How do I reset it?</h2> -<p>Go to <a href="https://npmjs.org/forgot">https://npmjs.org/forgot</a>.</p> +<p>Go to <a href="https://npmjs.com/forgot">https://npmjs.com/forgot</a>.</p> <h2 id="i-get-econnrefused-a-lot-what-s-up-">I get ECONNREFUSED a lot. What's up?</h2> <p>Either the registry is down, or node's DNS isn't able to reach out.</p> <p>To check if the registry is down, open up <a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a> in a web browser. This will also tell you if you are just unable to access the internet for some reason.</p> -<p>If the registry IS down, let us know by emailing <a href="mailto:support@npmjs.com">support@npmjs.com</a> +<p>If the registry IS down, let us know by emailing <a href="mailto:support@npmjs.com">support@npmjs.com</a> or posting an issue at <a href="https://github.com/npm/npm/issues">https://github.com/npm/npm/issues</a>. If it's down for the world (and not just on your local network) then we're probably already being pinged about it.</p> <p>You can also often get a faster response by visiting the #npm channel on Freenode IRC.</p> <h2 id="why-no-namespaces-">Why no namespaces?</h2> -<p>Please see this discussion: <a href="https://github.com/npm/npm/issues/798">https://github.com/npm/npm/issues/798</a></p> -<p>tl;dr - It doesn't actually make things better, and can make them worse.</p> -<p>If you want to namespace your own packages, you may: simply use the -<code>-</code> character to separate the names. npm is a mostly anarchic system. -There is not sufficient need to impose namespace rules on everyone.</p> +<p>npm has only one global namespace. If you want to namespace your own packages, +you may: simply use the <code>-</code> character to separate the names. npm is a mostly +anarchic system. There is not sufficient need to impose namespace rules on +everyone.</p> +<p>As of 2.0, npm supports scoped packages, which allow you to publish a group of +related modules without worrying about name collisions.</p> +<p>Every npm user owns the scope associated with their username. For example, the +user named <code>npm</code> owns the scope <code>@npm</code>. Scoped packages are published inside a +scope by naming them as if they were files under the scope directory, e.g., by +setting <code>name</code> in <code>package.json</code> to <code>@npm/npm</code>.</p> +<p>Scoped packages can coexist with public npm packages in a private npm registry. +At present (2014-11-04) scoped packages may NOT be published to the public npm +registry.</p> +<p>Unscoped packages can only depend on other unscoped packages. Scoped packages +can depend on packages from their own scope, a different scope, or the public +registry (unscoped).</p> +<p>For the current documentation of scoped packages, see +<a href="https://docs.npmjs.com/misc/scope">https://docs.npmjs.com/misc/scope</a></p> +<p>References:</p> +<ol> +<li><p>For the reasoning behind the "one global namespace", please see this +discussion: <a href="https://github.com/npm/npm/issues/798">https://github.com/npm/npm/issues/798</a> (TL;DR: It doesn't +actually make things better, and can make them worse.)</p> +</li> +<li><p>For the pre-implementation discussion of the scoped package feature, see +this discussion: <a href="https://github.com/npm/npm/issues/5239">https://github.com/npm/npm/issues/5239</a></p> +</li> +</ol> <h2 id="who-does-npm-">Who does npm?</h2> <p>npm was originally written by Isaac Z. Schlueter, and many others have contributed to it, some of them quite substantially.</p> -<p>The npm open source project, The npm Registry, and <a href="https://www.npmjs.org">the community +<p>The npm open source project, The npm Registry, and <a href="https://www.npmjs.com">the community website</a> are maintained and operated by the good folks at <a href="http://www.npmjs.com">npm, Inc.</a></p> <h2 id="i-have-a-question-or-request-not-addressed-here-where-should-i-put-it-">I have a question or request not addressed here. Where should I put it?</h2> @@ -284,5 +307,5 @@ good folks at <a href="http://www.npmjs.com">npm, Inc.</a></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-faq — npm@2.1.6</p> +<p id="footer">npm-faq — npm@2.1.18</p> |