diff options
| author | Kat Marchán <kzm@sykosomatic.org> | 2016-12-18 20:22:09 -0800 |
|---|---|---|
| committer | Myles Borins <myles.borins@gmail.com> | 2016-12-28 15:30:50 -0500 |
| commit | 9946519fba73687d34dccd5813808252a1973f3c (patch) | |
| tree | 74d7194d2a00743bcd905027195e7e8000c5ac5a /deps/npm/html | |
| parent | 4d3b487b791606ea965f6280ce0eeea03d79b660 (diff) | |
| download | node-new-9946519fba73687d34dccd5813808252a1973f3c.tar.gz | |
deps: upgrade npm to 4.0.5
PR-URL: https://github.com/nodejs/node/pull/10330
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Diffstat (limited to 'deps/npm/html')
69 files changed, 353 insertions, 287 deletions
diff --git a/deps/npm/html/doc/README.html b/deps/npm/html/doc/README.html index 4aa3cc5e47..0d97ebb015 100644 --- a/deps/npm/html/doc/README.html +++ b/deps/npm/html/doc/README.html @@ -10,7 +10,7 @@ <div id="wrapper"> <h1><a href="cli/npm.html">npm</a></h1> <p>a JavaScript package manager</p> -<p><a href="https://travis-ci.org/npm/npm"><img src="https://img.shields.io/travis/npm/npm/master.svg" alt="Build Status"></a></p> +<p><a href="https://travis-ci.org/npm/npm"><img src="https://img.shields.io/travis/npm/npm/latest.svg" alt="Build Status"></a></p> <h2 id="synopsis">SYNOPSIS</h2> <p>This is just enough info to get you up and running.</p> <p>Much more info available via <code>npm help</code> once it's installed.</p> @@ -27,11 +27,11 @@ registries</a>.</p> terms of use for the default public registry are available at <a href="https://www.npmjs.com">https://www.npmjs.com</a>.</p> <h2 id="super-easy-install">Super Easy Install</h2> -<p>npm is bundled with <a href="http://nodejs.org/download/">node</a>.</p> +<p>npm is bundled with <a href="https://nodejs.org/en/download/">node</a>.</p> <h3 id="windows-computers">Windows Computers</h3> -<p><a href="http://nodejs.org/download/">Get the MSI</a>. npm is in it.</p> +<p><a href="https://nodejs.org/en/download/">Get the MSI</a>. npm is in it.</p> <h3 id="apple-macintosh-computers">Apple Macintosh Computers</h3> -<p><a href="http://nodejs.org/download/">Get the pkg</a>. npm is in it.</p> +<p><a href="https://nodejs.org/en/download/">Get the pkg</a>. npm is in it.</p> <h3 id="other-sorts-of-unices">Other Sorts of Unices</h3> <p>Run <code>make install</code>. npm will be installed with node.</p> <p>If you want a more fancy pants install (a different version, customized @@ -106,7 +106,7 @@ you should <a href="https://docs.npmjs.com/misc/developers">read this</a></p> </ul> <p>Be sure to include <em>all</em> of the output from the npm command that didn't work as expected. The <code>npm-debug.log</code> file is also helpful to provide.</p> -<p>You can also look for isaacs in #node.js on irc://irc.freenode.net. He +<p>You can also look for isaacs in #node.js on irc://irc.freenode.net. She will no doubt tell you to put the output in a gist or email.</p> <h2 id="see-also">SEE ALSO</h2> <ul> @@ -126,5 +126,5 @@ will no doubt tell you to put the output in a gist or email.</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"><a href="../doc/README.html">README</a> — npm@3.10.10</p> +<p id="footer"><a href="../doc/README.html">README</a> — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-access.html b/deps/npm/html/doc/cli/npm-access.html index fdc0cb756e..80a1da3423 100644 --- a/deps/npm/html/doc/cli/npm-access.html +++ b/deps/npm/html/doc/cli/npm-access.html @@ -84,5 +84,5 @@ with an HTTP 402 status code (logically enough), unless you use <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@3.10.10</p> +<p id="footer">npm-access — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-adduser.html b/deps/npm/html/doc/cli/npm-adduser.html index 9ade2746aa..9f6ccada72 100644 --- a/deps/npm/html/doc/cli/npm-adduser.html +++ b/deps/npm/html/doc/cli/npm-adduser.html @@ -30,7 +30,8 @@ your existing record.</p> <h3 id="registry">registry</h3> <p>Default: <a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a></p> <p>The base URL of the npm package registry. If <code>scope</code> is also specified, -this registry will only be used for packages with that scope. See <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code>.</p> +this registry will only be used for packages with that scope. <code>scope</code> defaults +to the scope of the project directory you're currently in, if any. See <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code>.</p> <h3 id="scope">scope</h3> <p>Default: none</p> <p>If specified, the user and login credentials given will be associated @@ -72,5 +73,5 @@ over any global configuration.</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-adduser — npm@3.10.10</p> +<p id="footer">npm-adduser — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-bin.html b/deps/npm/html/doc/cli/npm-bin.html index 8d408216a9..57a372baff 100644 --- a/deps/npm/html/doc/cli/npm-bin.html +++ b/deps/npm/html/doc/cli/npm-bin.html @@ -35,5 +35,5 @@ <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-bin — npm@3.10.10</p> +<p id="footer">npm-bin — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-bugs.html b/deps/npm/html/doc/cli/npm-bugs.html index d5b9edea56..607d245c27 100644 --- a/deps/npm/html/doc/cli/npm-bugs.html +++ b/deps/npm/html/doc/cli/npm-bugs.html @@ -55,5 +55,5 @@ a <code>package.json</code> in the current folder and use the <code>name</code> <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-bugs — npm@3.10.10</p> +<p id="footer">npm-bugs — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-build.html b/deps/npm/html/doc/cli/npm-build.html index 73c796c233..5f89aca15c 100644 --- a/deps/npm/html/doc/cli/npm-build.html +++ b/deps/npm/html/doc/cli/npm-build.html @@ -40,5 +40,5 @@ directly, run:</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-build — npm@3.10.10</p> +<p id="footer">npm-build — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-bundle.html b/deps/npm/html/doc/cli/npm-bundle.html index 1f256d222d..41a4229c99 100644 --- a/deps/npm/html/doc/cli/npm-bundle.html +++ b/deps/npm/html/doc/cli/npm-bundle.html @@ -31,5 +31,5 @@ install packages into the local space.</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-bundle — npm@3.10.10</p> +<p id="footer">npm-bundle — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-cache.html b/deps/npm/html/doc/cli/npm-cache.html index 883f07ffb5..1b6b34adb9 100644 --- a/deps/npm/html/doc/cli/npm-cache.html +++ b/deps/npm/html/doc/cli/npm-cache.html @@ -81,5 +81,5 @@ they do not make an HTTP request to the registry.</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-cache — npm@3.10.10</p> +<p id="footer">npm-cache — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-completion.html b/deps/npm/html/doc/cli/npm-completion.html index 1be550a7dd..2f5cad2d33 100644 --- a/deps/npm/html/doc/cli/npm-completion.html +++ b/deps/npm/html/doc/cli/npm-completion.html @@ -43,5 +43,5 @@ completions based on the arguments.</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-completion — npm@3.10.10</p> +<p id="footer">npm-completion — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-config.html b/deps/npm/html/doc/cli/npm-config.html index 8940698b4a..9036bf84d5 100644 --- a/deps/npm/html/doc/cli/npm-config.html +++ b/deps/npm/html/doc/cli/npm-config.html @@ -67,5 +67,5 @@ global config.</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-config — npm@3.10.10</p> +<p id="footer">npm-config — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-dedupe.html b/deps/npm/html/doc/cli/npm-dedupe.html index 40cbd9f23a..e822dd5e65 100644 --- a/deps/npm/html/doc/cli/npm-dedupe.html +++ b/deps/npm/html/doc/cli/npm-dedupe.html @@ -61,5 +61,5 @@ result in new modules being installed.</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-dedupe — npm@3.10.10</p> +<p id="footer">npm-dedupe — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-deprecate.html b/deps/npm/html/doc/cli/npm-deprecate.html index a8476c51b1..8402c36fca 100644 --- a/deps/npm/html/doc/cli/npm-deprecate.html +++ b/deps/npm/html/doc/cli/npm-deprecate.html @@ -38,5 +38,5 @@ something like this:</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-deprecate — npm@3.10.10</p> +<p id="footer">npm-deprecate — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-dist-tag.html b/deps/npm/html/doc/cli/npm-dist-tag.html index 3b66f87f78..b1b5c038bf 100644 --- a/deps/npm/html/doc/cli/npm-dist-tag.html +++ b/deps/npm/html/doc/cli/npm-dist-tag.html @@ -66,7 +66,6 @@ example, <code>v1.4</code> cannot be used as a tag, because it is interpreted by 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">npm-tag(1)</a></li> <li><a href="../cli/npm-publish.html">npm-publish(1)</a></li> <li><a href="../cli/npm-install.html">npm-install(1)</a></li> <li><a href="../cli/npm-dedupe.html">npm-dedupe(1)</a></li> @@ -87,5 +86,5 @@ begin with a number or the letter <code>v</code>.</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-dist-tag — npm@3.10.10</p> +<p id="footer">npm-dist-tag — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-docs.html b/deps/npm/html/doc/cli/npm-docs.html index 265c35be15..a713ca1f3a 100644 --- a/deps/npm/html/doc/cli/npm-docs.html +++ b/deps/npm/html/doc/cli/npm-docs.html @@ -56,5 +56,5 @@ the current folder and use the <code>name</code> property.</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-docs — npm@3.10.10</p> +<p id="footer">npm-docs — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-edit.html b/deps/npm/html/doc/cli/npm-edit.html index 60e0a3b516..db4eba4111 100644 --- a/deps/npm/html/doc/cli/npm-edit.html +++ b/deps/npm/html/doc/cli/npm-edit.html @@ -49,5 +49,5 @@ or <code>"notepad"</code> on Windows.</li> <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-edit — npm@3.10.10</p> +<p id="footer">npm-edit — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-explore.html b/deps/npm/html/doc/cli/npm-explore.html index 29d5829b5d..2fb651064c 100644 --- a/deps/npm/html/doc/cli/npm-explore.html +++ b/deps/npm/html/doc/cli/npm-explore.html @@ -49,5 +49,5 @@ Windows</li> <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-explore — npm@3.10.10</p> +<p id="footer">npm-explore — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-help-search.html b/deps/npm/html/doc/cli/npm-help-search.html index 107687584d..7a7980a97d 100644 --- a/deps/npm/html/doc/cli/npm-help-search.html +++ b/deps/npm/html/doc/cli/npm-help-search.html @@ -45,5 +45,5 @@ where the terms were found in the documentation.</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-help-search — npm@3.10.10</p> +<p id="footer">npm-help-search — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-help.html b/deps/npm/html/doc/cli/npm-help.html index feb154a521..7249903ccc 100644 --- a/deps/npm/html/doc/cli/npm-help.html +++ b/deps/npm/html/doc/cli/npm-help.html @@ -50,5 +50,5 @@ matches are equivalent to specifying a topic name.</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-help — npm@3.10.10</p> +<p id="footer">npm-help — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-init.html b/deps/npm/html/doc/cli/npm-init.html index 5474d8392a..b4cec6b416 100644 --- a/deps/npm/html/doc/cli/npm-init.html +++ b/deps/npm/html/doc/cli/npm-init.html @@ -48,5 +48,5 @@ defaults and not prompt you for any options.</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-init — npm@3.10.10</p> +<p id="footer">npm-init — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-install-test.html b/deps/npm/html/doc/cli/npm-install-test.html index 428e0c7739..d283317a71 100644 --- a/deps/npm/html/doc/cli/npm-install-test.html +++ b/deps/npm/html/doc/cli/npm-install-test.html @@ -42,5 +42,5 @@ takes exactly the same arguments as <code>npm install</code>.</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-install-test — npm@3.10.10</p> +<p id="footer">npm-install-test — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-install.html b/deps/npm/html/doc/cli/npm-install.html index 8c4575f949..c647781dcf 100644 --- a/deps/npm/html/doc/cli/npm-install.html +++ b/deps/npm/html/doc/cli/npm-install.html @@ -269,6 +269,9 @@ privately for itself.</p> <p>See <a href="../files/npm-folders.html">npm-folders(5)</a> for a more detailed description of the specific folder structures that npm creates.</p> <h3 id="limitations-of-npm-s-install-algorithm">Limitations of npm's Install Algorithm</h3> +<p>npm will refuse to install any package with an identical name to the +current package. This can be overridden with the <code>--force</code> flag, but in +most cases can simply be addressed by changing the local package name.</p> <p>There are some very rare and pathological edge-cases where a cycle can cause npm to try to install a never-ending tree of packages. Here is the simplest case:</p> @@ -296,7 +299,7 @@ affects a real use-case, it will be investigated.</p> <li><a href="../misc/npm-config.html">npm-config(7)</a></li> <li><a href="../files/npmrc.html">npmrc(5)</a></li> <li><a href="../misc/npm-registry.html">npm-registry(7)</a></li> -<li><a href="../cli/npm-tag.html">npm-tag(1)</a></li> +<li><a href="../cli/npm-dist-tag.html">npm-dist-tag(1)</a></li> <li><a href="../cli/npm-uninstall.html">npm-uninstall(1)</a></li> <li><a href="../cli/npm-shrinkwrap.html">npm-shrinkwrap(1)</a></li> <li><a href="../files/package.json.html">package.json(5)</a></li> @@ -313,5 +316,5 @@ affects a real use-case, it will be investigated.</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-install — npm@3.10.10</p> +<p id="footer">npm-install — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-link.html b/deps/npm/html/doc/cli/npm-link.html index d7aed7df34..f10b790bc2 100644 --- a/deps/npm/html/doc/cli/npm-link.html +++ b/deps/npm/html/doc/cli/npm-link.html @@ -74,5 +74,5 @@ include that scope, e.g.</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-link — npm@3.10.10</p> +<p id="footer">npm-link — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-logout.html b/deps/npm/html/doc/cli/npm-logout.html index a6d86e64b5..6543b57851 100644 --- a/deps/npm/html/doc/cli/npm-logout.html +++ b/deps/npm/html/doc/cli/npm-logout.html @@ -27,7 +27,7 @@ connected to that scope, if set.</p> <p>The base URL of the npm package registry. If <code>scope</code> is also specified, it takes precedence.</p> <h3 id="scope">scope</h3> -<p>Default: none</p> +<p>Default: The scope of your current project, if any, otherwise none.</p> <p>If specified, you will be logged out of the specified scope. See <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code>.</p> <pre><code>npm logout --scope=@myco </code></pre><h2 id="see-also">SEE ALSO</h2> @@ -51,5 +51,5 @@ it takes precedence.</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-logout — npm@3.10.10</p> +<p id="footer">npm-logout — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-ls.html b/deps/npm/html/doc/cli/npm-ls.html index e3e3e60343..1b5d61bd38 100644 --- a/deps/npm/html/doc/cli/npm-ls.html +++ b/deps/npm/html/doc/cli/npm-ls.html @@ -21,7 +21,7 @@ installed, as well as their dependencies, in a tree-structure.</p> limit the results to only the paths to the packages named. Note that nested packages will <em>also</em> show the paths to the specified packages. For example, running <code>npm ls promzard</code> in npm's source tree will show:</p> -<pre><code>npm@3.10.10 /path/to/npm +<pre><code>npm@4.0.5 /path/to/npm └─┬ init-package-json@0.0.4 └── promzard@0.1.5 </code></pre><p>It will print out extraneous, missing, and invalid packages.</p> @@ -104,5 +104,5 @@ project.</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-ls — npm@3.10.10</p> +<p id="footer">npm-ls — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-outdated.html b/deps/npm/html/doc/cli/npm-outdated.html index 5c06e18fb3..04a0da5155 100644 --- a/deps/npm/html/doc/cli/npm-outdated.html +++ b/deps/npm/html/doc/cli/npm-outdated.html @@ -116,5 +116,5 @@ project.</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-outdated — npm@3.10.10</p> +<p id="footer">npm-outdated — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-owner.html b/deps/npm/html/doc/cli/npm-owner.html index 9ec584f4ec..9f6d4db959 100644 --- a/deps/npm/html/doc/cli/npm-owner.html +++ b/deps/npm/html/doc/cli/npm-owner.html @@ -51,5 +51,5 @@ that is not implemented at this time.</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-owner — npm@3.10.10</p> +<p id="footer">npm-owner — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-pack.html b/deps/npm/html/doc/cli/npm-pack.html index 74682f5281..92cea26747 100644 --- a/deps/npm/html/doc/cli/npm-pack.html +++ b/deps/npm/html/doc/cli/npm-pack.html @@ -41,5 +41,5 @@ overwritten the second time.</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-pack — npm@3.10.10</p> +<p id="footer">npm-pack — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-ping.html b/deps/npm/html/doc/cli/npm-ping.html index b48db8ab63..f094762e62 100644 --- a/deps/npm/html/doc/cli/npm-ping.html +++ b/deps/npm/html/doc/cli/npm-ping.html @@ -32,5 +32,5 @@ <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-ping — npm@3.10.10</p> +<p id="footer">npm-ping — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-prefix.html b/deps/npm/html/doc/cli/npm-prefix.html index 171c7ca263..906de75ff8 100644 --- a/deps/npm/html/doc/cli/npm-prefix.html +++ b/deps/npm/html/doc/cli/npm-prefix.html @@ -38,5 +38,5 @@ to contain a package.json file unless <code>-g</code> is also specified.</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-prefix — npm@3.10.10</p> +<p id="footer">npm-prefix — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-prune.html b/deps/npm/html/doc/cli/npm-prune.html index 5000f2c75c..9e40f28103 100644 --- a/deps/npm/html/doc/cli/npm-prune.html +++ b/deps/npm/html/doc/cli/npm-prune.html @@ -40,5 +40,5 @@ negate <code>NODE_ENV</code> being set to <code>production</code>.</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-prune — npm@3.10.10</p> +<p id="footer">npm-prune — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-publish.html b/deps/npm/html/doc/cli/npm-publish.html index c3272d3cdb..a6959ce0a4 100644 --- a/deps/npm/html/doc/cli/npm-publish.html +++ b/deps/npm/html/doc/cli/npm-publish.html @@ -61,7 +61,7 @@ packs them into a tarball to be uploaded to the registry.</p> <li><a href="../cli/npm-adduser.html">npm-adduser(1)</a></li> <li><a href="../cli/npm-owner.html">npm-owner(1)</a></li> <li><a href="../cli/npm-deprecate.html">npm-deprecate(1)</a></li> -<li><a href="../cli/npm-tag.html">npm-tag(1)</a></li> +<li><a href="../cli/npm-dist-tag.html">npm-dist-tag(1)</a></li> <li><a href="../cli/npm-pack.html">npm-pack(1)</a></li> </ul> @@ -76,5 +76,5 @@ packs them into a tarball to be uploaded to the registry.</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-publish — npm@3.10.10</p> +<p id="footer">npm-publish — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-rebuild.html b/deps/npm/html/doc/cli/npm-rebuild.html index c975efca6b..b2d0670189 100644 --- a/deps/npm/html/doc/cli/npm-rebuild.html +++ b/deps/npm/html/doc/cli/npm-rebuild.html @@ -35,5 +35,5 @@ the new binary.</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-rebuild — npm@3.10.10</p> +<p id="footer">npm-rebuild — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-repo.html b/deps/npm/html/doc/cli/npm-repo.html index 30b18957ca..83af687516 100644 --- a/deps/npm/html/doc/cli/npm-repo.html +++ b/deps/npm/html/doc/cli/npm-repo.html @@ -41,5 +41,5 @@ a <code>package.json</code> in the current folder and use the <code>name</code> <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-repo — npm@3.10.10</p> +<p id="footer">npm-repo — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-restart.html b/deps/npm/html/doc/cli/npm-restart.html index ceb270c6d8..6d4c455659 100644 --- a/deps/npm/html/doc/cli/npm-restart.html +++ b/deps/npm/html/doc/cli/npm-restart.html @@ -53,5 +53,5 @@ behavior will be accompanied by an increase in major version number</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-restart — npm@3.10.10</p> +<p id="footer">npm-restart — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-root.html b/deps/npm/html/doc/cli/npm-root.html index 44c63f0c18..343790ab57 100644 --- a/deps/npm/html/doc/cli/npm-root.html +++ b/deps/npm/html/doc/cli/npm-root.html @@ -35,5 +35,5 @@ <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-root — npm@3.10.10</p> +<p id="footer">npm-root — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-run-script.html b/deps/npm/html/doc/cli/npm-run-script.html index 27fcfc9345..d68504647a 100644 --- a/deps/npm/html/doc/cli/npm-run-script.html +++ b/deps/npm/html/doc/cli/npm-run-script.html @@ -39,8 +39,11 @@ you should write:</p> <pre><code>"scripts": {"test": "tap test/\*.js"} </code></pre><p>instead of <code>"scripts": {"test": "node_modules/.bin/tap test/\*.js"}</code> to run your tests.</p> <p><code>npm run</code> sets the <code>NODE</code> environment variable to the <code>node</code> executable with -which <code>npm</code> is executed. Also, the directory within which it resides is added to the -<code>PATH</code>, if the <code>node</code> executable is not in the <code>PATH</code>.</p> +which <code>npm</code> is executed. Also, if the <code>--scripts-prepend-node-path</code> is passed, +the directory within which <code>node</code> resides is added to the +<code>PATH</code>. If <code>--scripts-prepend-node-path=auto</code> is passed (which has been the +default in <code>npm</code> v3), this is only performed when that <code>node</code> executable is +not found in the <code>PATH</code>.</p> <p>If you try to run a script without having a <code>node_modules</code> directory and it fails, you will be given a warning to run <code>npm install</code>, just in case you've forgotten.</p> <h2 id="see-also">SEE ALSO</h2> @@ -63,5 +66,5 @@ you will be given a warning to run <code>npm install</code>, just in case you <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-run-script — npm@3.10.10</p> +<p id="footer">npm-run-script — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-search.html b/deps/npm/html/doc/cli/npm-search.html index ed10e4c422..015d4a3ddb 100644 --- a/deps/npm/html/doc/cli/npm-search.html +++ b/deps/npm/html/doc/cli/npm-search.html @@ -11,15 +11,47 @@ <h1><a href="../cli/npm-search.html">npm-search</a></h1> <p>Search for packages</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm search [-l|--long] [search terms ...] +<pre><code>npm search [-l|--long] [--json] [--parseable] [--no-description] [search terms ...] aliases: s, se, find </code></pre><h2 id="description">DESCRIPTION</h2> -<p>Search the registry for packages matching the search terms.</p> -<p>If a term starts with <code>/</code>, then it's interpreted as a regular expression. -A trailing <code>/</code> will be ignored in this case. (Note that many regular -expression characters must be escaped or quoted in most shells.)</p> +<p>Search the registry for packages matching the search terms. <code>npm search</code> +performs a linear, incremental, lexically-ordered search through package +metadata for all files in the registry. If color is enabled, it will further +highlight the matches in the results.</p> +<p>Additionally, using the <code>--searchopts</code> and <code>--searchexclude</code> options paired with +more search terms will respectively include and exclude further patterns. The +main difference between <code>--searchopts</code> and the standard search terms is that the +former does not highlight results in the output and can be used for more +fine-grained filtering. Additionally, both of these can be added to <code>.npmrc</code> for +default search filtering behavior.</p> +<p>Search also allows targeting of maintainers in search results, by prefixing +their npm username with <code>=</code>.</p> +<p>If a term starts with <code>/</code>, then it's interpreted as a regular expression and +supports standard JavaScript RegExp syntax. A trailing <code>/</code> will be ignored in +this case. (Note that many regular expression characters must be escaped or +quoted in most shells.)</p> +<h3 id="a-note-on-caching">A Note on caching</h3> <h2 id="configuration">CONFIGURATION</h2> +<h3 id="description">description</h3> +<ul> +<li>Default: true</li> +<li>Type: Boolean</li> +</ul> +<p>Used as <code>--no-description</code>, disables search matching in package descriptions and +suppresses display of that field in results.</p> +<h3 id="json">json</h3> +<ul> +<li>Default: false</li> +<li>Type: Boolean</li> +</ul> +<p>Output search results as a JSON array.</p> +<h3 id="parseable">parseable</h3> +<ul> +<li>Default: false</li> +<li>Type: Boolean</li> +</ul> +<p>Output search results as lines with tab-separated columns.</p> <h3 id="long">long</h3> <ul> <li>Default: false</li> @@ -29,14 +61,34 @@ expression characters must be escaped or quoted in most shells.)</p> lines. When disabled (default) search results are truncated to fit neatly on a single line. Modules with extremely long names will fall on multiple lines.</p> +<h3 id="searchopts">searchopts</h3> +<ul> +<li>Default: ""</li> +<li>Type: String</li> +</ul> +<p>Space-separated options that are always passed to search.</p> +<h3 id="searchexclude">searchexclude</h3> +<ul> +<li>Default: ""</li> +<li>Type: String</li> +</ul> +<p>Space-separated options that limit the results from search.</p> +<h3 id="searchstaleness">searchstaleness</h3> +<ul> +<li>Default: 900 (15 minutes)</li> +<li>Type: Number</li> +</ul> +<p>The age of the cache, in seconds, before another registry request is made.</p> <h3 id="registry">registry</h3> <ul> <li>Default: <a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a></li> -<li>Type : url</li> +<li>Type: url</li> </ul> -<p>Search the specified registry for modules. If you have configured npm to point to a different default registry, -such as your internal private module repository, <code>npm search</code> will default to that registry when searching. -Pass a different registry url such as the default above in order to override this setting.</p> +<p>Search the specified registry for modules. If you have configured npm to point +to a different default registry, such as your internal private module +repository, <code>npm search</code> will default to that registry when searching. Pass a +different registry url such as the default above in order to override this +setting.</p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../misc/npm-registry.html">npm-registry(7)</a></li> @@ -57,5 +109,5 @@ Pass a different registry url such as the default above in order to override thi <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-search — npm@3.10.10</p> +<p id="footer">npm-search — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-shrinkwrap.html b/deps/npm/html/doc/cli/npm-shrinkwrap.html index bfe3410125..0f80895acf 100644 --- a/deps/npm/html/doc/cli/npm-shrinkwrap.html +++ b/deps/npm/html/doc/cli/npm-shrinkwrap.html @@ -139,12 +139,16 @@ already installed, since that would result in a shrinkwrap that wouldn't actually work. Similarly, the command will fail if there are extraneous packages (not referenced by <code>package.json</code>), since that would indicate that <code>package.json</code> is not correct.</p> -<p>Since <code>npm shrinkwrap</code> is intended to lock down your dependencies for -production use, <code>devDependencies</code> will not be included unless you -explicitly set the <code>--dev</code> flag when you run <code>npm shrinkwrap</code>. If -installed <code>devDependencies</code> are excluded, then npm will print a -warning. If you want them to be installed with your module by -default, please consider adding them to <code>dependencies</code> instead.</p> +<p>Starting with npm v4.0.1, <code>devDependencies</code> are included when you run +<code>npm shrinkwrap</code> and follow the usual rules as to when they're installed. +As of npm v3.10.8, if you run <code>npm install --only=production</code> or +<code>npm install --production</code> with a shrinkwrap including your development +dependencies they won't be installed. Similarly, if the environment +variable <code>NODE_ENV</code> is <code>production</code> then they won't be installed. If you +need compatibility with versions of npm prior to v3.10.8 or otherwise +don't want them in your shrinkwrap you can exclude development +dependencies with: +<code>npm shrinkwrap --only=prod</code> or <code>npm shrinkwrap --production</code>.</p> <p>If shrinkwrapped package A depends on shrinkwrapped package B, B's shrinkwrap will not be used as part of the installation of A. However, because A's shrinkwrap is constructed from a valid installation of B @@ -176,5 +180,5 @@ contents rather than versions.</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-shrinkwrap — npm@3.10.10</p> +<p id="footer">npm-shrinkwrap — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-star.html b/deps/npm/html/doc/cli/npm-star.html index 01c593c461..2564d61dfc 100644 --- a/deps/npm/html/doc/cli/npm-star.html +++ b/deps/npm/html/doc/cli/npm-star.html @@ -36,5 +36,5 @@ a vaguely positive way to show that you care.</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-star — npm@3.10.10</p> +<p id="footer">npm-star — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-stars.html b/deps/npm/html/doc/cli/npm-stars.html index 4d470fd4ba..a4889bd84d 100644 --- a/deps/npm/html/doc/cli/npm-stars.html +++ b/deps/npm/html/doc/cli/npm-stars.html @@ -36,5 +36,5 @@ you will most certainly enjoy this command.</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-stars — npm@3.10.10</p> +<p id="footer">npm-stars — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-start.html b/deps/npm/html/doc/cli/npm-start.html index f193608014..65c229ec95 100644 --- a/deps/npm/html/doc/cli/npm-start.html +++ b/deps/npm/html/doc/cli/npm-start.html @@ -39,5 +39,5 @@ more details.</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-start — npm@3.10.10</p> +<p id="footer">npm-start — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-stop.html b/deps/npm/html/doc/cli/npm-stop.html index 082b2560c7..277b5a845e 100644 --- a/deps/npm/html/doc/cli/npm-stop.html +++ b/deps/npm/html/doc/cli/npm-stop.html @@ -34,5 +34,5 @@ <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-stop — npm@3.10.10</p> +<p id="footer">npm-stop — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-tag.html b/deps/npm/html/doc/cli/npm-tag.html deleted file mode 100644 index 2270e1e3f1..0000000000 --- a/deps/npm/html/doc/cli/npm-tag.html +++ /dev/null @@ -1,67 +0,0 @@ -<!doctype html> -<html> - <title>npm-tag</title> - <meta charset="utf-8"> - <link rel="stylesheet" type="text/css" href="../../static/style.css"> - <link rel="canonical" href="https://www.npmjs.org/doc/cli/npm-tag.html"> - <script async=true src="../../static/toc.js"></script> - - <body> - <div id="wrapper"> - -<h1><a href="../cli/npm-tag.html">npm-tag</a></h1> <p>Tag a published version</p> -<h2 id="synopsis">SYNOPSIS</h2> -<pre><code>[DEPRECATED] npm tag <name>@<version> [<tag>] -See `dist-tag` -</code></pre><h2 id="description">DESCRIPTION</h2> -<p>THIS COMMAND IS DEPRECATED. See <a href="../cli/npm-dist-tag.html">npm-dist-tag(1)</a> for details.</p> -<p>Tags the specified version of the package with the specified tag, or the -<code>--tag</code> config if not specified.</p> -<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>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-publish.html">npm-publish(1)</a></li> -<li><a href="../cli/npm-install.html">npm-install(1)</a></li> -<li><a href="../cli/npm-dedupe.html">npm-dedupe(1)</a></li> -<li><a href="../misc/npm-registry.html">npm-registry(7)</a></li> -<li><a href="../cli/npm-config.html">npm-config(1)</a></li> -<li><a href="../misc/npm-config.html">npm-config(7)</a></li> -<li><a href="../cli/npm-dist-tag.html">npm-dist-tag(1)</a></li> -<li><a href="../files/npmrc.html">npmrc(5)</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-tag — npm@3.10.10</p> - diff --git a/deps/npm/html/doc/cli/npm-team.html b/deps/npm/html/doc/cli/npm-team.html index 02dffaae03..2fea57d08e 100644 --- a/deps/npm/html/doc/cli/npm-team.html +++ b/deps/npm/html/doc/cli/npm-team.html @@ -67,5 +67,5 @@ use the <code>npm access</code> command to grant or revoke the appropriate permi <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-team — npm@3.10.10</p> +<p id="footer">npm-team — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-test.html b/deps/npm/html/doc/cli/npm-test.html index c15a2fe233..041ce2130b 100644 --- a/deps/npm/html/doc/cli/npm-test.html +++ b/deps/npm/html/doc/cli/npm-test.html @@ -16,8 +16,6 @@ aliases: t, tst </code></pre><h2 id="description">DESCRIPTION</h2> <p>This runs a package's "test" script, if one was provided.</p> -<p>To run tests as a condition of installation, set the <code>npat</code> config to -true.</p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../cli/npm-run-script.html">npm-run-script(1)</a></li> @@ -38,5 +36,5 @@ true.</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-test — npm@3.10.10</p> +<p id="footer">npm-test — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-uninstall.html b/deps/npm/html/doc/cli/npm-uninstall.html index 1ed389ac26..b1d9de7809 100644 --- a/deps/npm/html/doc/cli/npm-uninstall.html +++ b/deps/npm/html/doc/cli/npm-uninstall.html @@ -60,5 +60,5 @@ npm uninstall dtrace-provider --save-optional <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-uninstall — npm@3.10.10</p> +<p id="footer">npm-uninstall — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-unpublish.html b/deps/npm/html/doc/cli/npm-unpublish.html index 4e085352ad..147e42221a 100644 --- a/deps/npm/html/doc/cli/npm-unpublish.html +++ b/deps/npm/html/doc/cli/npm-unpublish.html @@ -47,5 +47,5 @@ package again, a new version number must be used.</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-unpublish — npm@3.10.10</p> +<p id="footer">npm-unpublish — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-update.html b/deps/npm/html/doc/cli/npm-update.html index 809475745e..c2b8b18d48 100644 --- a/deps/npm/html/doc/cli/npm-update.html +++ b/deps/npm/html/doc/cli/npm-update.html @@ -118,5 +118,5 @@ be <em>downgraded</em>.</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-update — npm@3.10.10</p> +<p id="footer">npm-update — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-version.html b/deps/npm/html/doc/cli/npm-version.html index bc58045dc7..adbfb7ab7c 100644 --- a/deps/npm/html/doc/cli/npm-version.html +++ b/deps/npm/html/doc/cli/npm-version.html @@ -79,6 +79,13 @@ and tag up to the server, and deletes the <code>build/temp</code> directory.</p> <li>Type: Boolean</li> </ul> <p>Commit and tag the version change.</p> +<h3 id="sign-git-tag">sign-git-tag</h3> +<ul> +<li>Default: false</li> +<li>Type: Boolean</li> +</ul> +<p>Pass the <code>-s</code> flag to git to sign the tag.</p> +<p>Note that you must have a default GPG key set up in your git config for this to work properly.</p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../cli/npm-init.html">npm-init(1)</a></li> @@ -100,5 +107,5 @@ and tag up to the server, and deletes the <code>build/temp</code> directory.</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-version — npm@3.10.10</p> +<p id="footer">npm-version — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-view.html b/deps/npm/html/doc/cli/npm-view.html index 9b7651fcce..f1de2303d0 100644 --- a/deps/npm/html/doc/cli/npm-view.html +++ b/deps/npm/html/doc/cli/npm-view.html @@ -86,5 +86,5 @@ the field name.</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-view — npm@3.10.10</p> +<p id="footer">npm-view — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm-whoami.html b/deps/npm/html/doc/cli/npm-whoami.html index cc30465997..50ff32f00c 100644 --- a/deps/npm/html/doc/cli/npm-whoami.html +++ b/deps/npm/html/doc/cli/npm-whoami.html @@ -33,5 +33,5 @@ <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-whoami — npm@3.10.10</p> +<p id="footer">npm-whoami — npm@4.0.5</p> diff --git a/deps/npm/html/doc/cli/npm.html b/deps/npm/html/doc/cli/npm.html index 08b24220f3..44685d4a29 100644 --- a/deps/npm/html/doc/cli/npm.html +++ b/deps/npm/html/doc/cli/npm.html @@ -13,7 +13,7 @@ <h2 id="synopsis">SYNOPSIS</h2> <pre><code>npm <command> [args] </code></pre><h2 id="version">VERSION</h2> -<p>3.10.10</p> +<p>4.0.5</p> <h2 id="description">DESCRIPTION</h2> <p>npm is the package manager for the Node JavaScript platform. It puts modules in place so that node can find them, and manages dependency @@ -126,7 +126,7 @@ will no doubt tell you to put the output in a gist or email.</p> <p><a href="http://blog.izs.me/">Isaac Z. Schlueter</a> :: <a href="https://github.com/isaacs/">isaacs</a> :: <a href="http://twitter.com/izs">@izs</a> :: -<a href="mailto:i@izs.me">i@izs.me</a></p> +<a href="mailto:i@izs.me">i@izs.me</a></p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../cli/npm-help.html">npm-help(1)</a></li> @@ -150,5 +150,5 @@ will no doubt tell you to put the output in a gist or email.</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 — npm@3.10.10</p> +<p id="footer">npm — npm@4.0.5</p> diff --git a/deps/npm/html/doc/files/npm-folders.html b/deps/npm/html/doc/files/npm-folders.html index 0937d2a131..b54e1a3f4d 100644 --- a/deps/npm/html/doc/files/npm-folders.html +++ b/deps/npm/html/doc/files/npm-folders.html @@ -182,5 +182,5 @@ cannot be found elsewhere. See <code><a href="../files/package.json.html">packa <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-folders — npm@3.10.10</p> +<p id="footer">npm-folders — npm@4.0.5</p> diff --git a/deps/npm/html/doc/files/npm-global.html b/deps/npm/html/doc/files/npm-global.html index 0937d2a131..b54e1a3f4d 100644 --- a/deps/npm/html/doc/files/npm-global.html +++ b/deps/npm/html/doc/files/npm-global.html @@ -182,5 +182,5 @@ cannot be found elsewhere. See <code><a href="../files/package.json.html">packa <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-folders — npm@3.10.10</p> +<p id="footer">npm-folders — npm@4.0.5</p> diff --git a/deps/npm/html/doc/files/npm-json.html b/deps/npm/html/doc/files/npm-json.html index 3894c9ead6..392d8552f8 100644 --- a/deps/npm/html/doc/files/npm-json.html +++ b/deps/npm/html/doc/files/npm-json.html @@ -317,7 +317,7 @@ tarball or git URL.</p> <li><code>range1 || range2</code> Passes if either range1 or range2 are satisfied.</li> <li><code>git...</code> See 'Git URLs as Dependencies' below</li> <li><code>user/repo</code> See 'GitHub URLs' below</li> -<li><code>tag</code> A specific version tagged and published as <code>tag</code> See <code><a href="../cli/npm-tag.html">npm-tag(1)</a></code></li> +<li><code>tag</code> A specific version tagged and published as <code>tag</code> See <code><a href="../cli/npm-dist-tag.html">npm-dist-tag(1)</a></code></li> <li><code>path/path/path</code> See <a href="#local-paths">Local Paths</a> below</li> </ul> <p>For example, these are all valid:</p> @@ -357,8 +357,8 @@ included. For example:</p> "name": "foo", "version": "0.0.0", "dependencies": { - "express": "visionmedia/express", - "mocha": "visionmedia/mocha#4727d357ea", + "express": "expressjs/express", + "mocha": "mochajs/mocha#4727d357ea", "module": "user/repo#feature\/branch" } } @@ -392,7 +392,7 @@ object.</p> from the root of a package, and can be managed like any other npm configuration param. See <code><a href="../misc/npm-config.html">npm-config(7)</a></code> for more on the topic.</p> <p>For build steps that are not platform-specific, such as compiling -CoffeeScript or other languages to JavaScript, use the <code>prepublish</code> +CoffeeScript or other languages to JavaScript, use the <code>prepare</code> script to do this, and make the required package a devDependency.</p> <p>For example:</p> <pre><code>{ "name": "ethopia-waza", @@ -402,11 +402,11 @@ script to do this, and make the required package a devDependency.</p> "coffee-script": "~1.6.3" }, "scripts": { - "prepublish": "coffee -o lib/ -c src/waza.coffee" + "prepare": "coffee -o lib/ -c src/waza.coffee" }, "main": "lib/waza.js" } -</code></pre><p>The <code>prepublish</code> script will be run before publishing, so that users +</code></pre><p>The <code>prepare</code> script will be run before publishing, so that users can consume the functionality without requiring them to compile it themselves. In dev mode (ie, locally running <code>npm install</code>), it'll run this script as well, so that you can test it easily.</p> @@ -586,5 +586,5 @@ ignored.</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">package.json — npm@3.10.10</p> +<p id="footer">package.json — npm@4.0.5</p> diff --git a/deps/npm/html/doc/files/npmrc.html b/deps/npm/html/doc/files/npmrc.html index 151b0c0079..8385a103a3 100644 --- a/deps/npm/html/doc/files/npmrc.html +++ b/deps/npm/html/doc/files/npmrc.html @@ -35,11 +35,7 @@ override the setting in the globalconfig file.</p> example:</p> <pre><code>key[] = "first value" key[] = "second value" -</code></pre><p><strong>NOTE:</strong> Because local (per-project or per-user) <code>.npmrc</code> files can contain -sensitive credentials, they must be readable and writable <em>only</em> by your user -account (i.e. must have a mode of <code>0600</code>), otherwise they <em>will be ignored by -npm!</em></p> -<h4 id="comments">Comments</h4> +</code></pre><h4 id="comments">Comments</h4> <p>Lines in <code>.npmrc</code> files are interpreted as comments when they begin with a <code>;</code> or <code>#</code> character. <code>.npmrc</code> files are parsed by <a href="https://github.com/npm/ini">npm/ini</a>, which specifies this comment syntax.</p> <p>For example:</p> <pre><code># last modified: 01 Jan 2016 @@ -89,5 +85,5 @@ manner.</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">npmrc — npm@3.10.10</p> +<p id="footer">npmrc — npm@4.0.5</p> diff --git a/deps/npm/html/doc/files/package.json.html b/deps/npm/html/doc/files/package.json.html index 3894c9ead6..392d8552f8 100644 --- a/deps/npm/html/doc/files/package.json.html +++ b/deps/npm/html/doc/files/package.json.html @@ -317,7 +317,7 @@ tarball or git URL.</p> <li><code>range1 || range2</code> Passes if either range1 or range2 are satisfied.</li> <li><code>git...</code> See 'Git URLs as Dependencies' below</li> <li><code>user/repo</code> See 'GitHub URLs' below</li> -<li><code>tag</code> A specific version tagged and published as <code>tag</code> See <code><a href="../cli/npm-tag.html">npm-tag(1)</a></code></li> +<li><code>tag</code> A specific version tagged and published as <code>tag</code> See <code><a href="../cli/npm-dist-tag.html">npm-dist-tag(1)</a></code></li> <li><code>path/path/path</code> See <a href="#local-paths">Local Paths</a> below</li> </ul> <p>For example, these are all valid:</p> @@ -357,8 +357,8 @@ included. For example:</p> "name": "foo", "version": "0.0.0", "dependencies": { - "express": "visionmedia/express", - "mocha": "visionmedia/mocha#4727d357ea", + "express": "expressjs/express", + "mocha": "mochajs/mocha#4727d357ea", "module": "user/repo#feature\/branch" } } @@ -392,7 +392,7 @@ object.</p> from the root of a package, and can be managed like any other npm configuration param. See <code><a href="../misc/npm-config.html">npm-config(7)</a></code> for more on the topic.</p> <p>For build steps that are not platform-specific, such as compiling -CoffeeScript or other languages to JavaScript, use the <code>prepublish</code> +CoffeeScript or other languages to JavaScript, use the <code>prepare</code> script to do this, and make the required package a devDependency.</p> <p>For example:</p> <pre><code>{ "name": "ethopia-waza", @@ -402,11 +402,11 @@ script to do this, and make the required package a devDependency.</p> "coffee-script": "~1.6.3" }, "scripts": { - "prepublish": "coffee -o lib/ -c src/waza.coffee" + "prepare": "coffee -o lib/ -c src/waza.coffee" }, "main": "lib/waza.js" } -</code></pre><p>The <code>prepublish</code> script will be run before publishing, so that users +</code></pre><p>The <code>prepare</code> script will be run before publishing, so that users can consume the functionality without requiring them to compile it themselves. In dev mode (ie, locally running <code>npm install</code>), it'll run this script as well, so that you can test it easily.</p> @@ -586,5 +586,5 @@ ignored.</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">package.json — npm@3.10.10</p> +<p id="footer">package.json — npm@4.0.5</p> diff --git a/deps/npm/html/doc/index.html b/deps/npm/html/doc/index.html index 394e371da4..83baa43e6e 100644 --- a/deps/npm/html/doc/index.html +++ b/deps/npm/html/doc/index.html @@ -98,8 +98,6 @@ <p>Start a package</p> <h3 id="npm-stop-1-"><a href="cli/npm-stop.html">npm-stop(1)</a></h3> <p>Stop a package</p> -<h3 id="npm-tag-1-"><a href="cli/npm-tag.html">npm-tag(1)</a></h3> -<p>Tag a published version</p> <h3 id="npm-team-1-"><a href="cli/npm-team.html">npm-team(1)</a></h3> <p>Manage organization teams and team memberships</p> <h3 id="npm-test-1-"><a href="cli/npm-test.html">npm-test(1)</a></h3> @@ -162,5 +160,5 @@ <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-index — npm@3.10.10</p> +<p id="footer">npm-index — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-coding-style.html b/deps/npm/html/doc/misc/npm-coding-style.html index 93ab1a0e18..0873b5f82f 100644 --- a/deps/npm/html/doc/misc/npm-coding-style.html +++ b/deps/npm/html/doc/misc/npm-coding-style.html @@ -153,5 +153,5 @@ set to anything."</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-coding-style — npm@3.10.10</p> +<p id="footer">npm-coding-style — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-config.html b/deps/npm/html/doc/misc/npm-config.html index 75720461f7..c4dca1bc18 100644 --- a/deps/npm/html/doc/misc/npm-config.html +++ b/deps/npm/html/doc/misc/npm-config.html @@ -24,7 +24,10 @@ interpreted as a configuration parameter. For example, putting configuration parameter to <code>bar</code>. Any environment configurations that are not given a value will be given the value of <code>true</code>. Config values are case-insensitive, so <code>NPM_CONFIG_FOO=bar</code> will work the -same.</p> +same. However, please note that inside <a href="/misc/scripts">npm-scripts</a> +npm will set it's own environment variables and Node will prefer +those lowercase versions over any uppercase ones that you might set. +For details see <a href="https://github.com/npm/npm/issues/14528">this issue</a>.</p> <h3 id="npmrc-files">npmrc Files</h3> <p>The four relevant files are:</p> <ul> @@ -236,8 +239,6 @@ e.g., <code>npm outdated --depth 9999</code></p> <li>Type: Boolean</li> </ul> <p>Install <code>dev-dependencies</code> along with packages.</p> -<p>Note that <code>dev-dependencies</code> are also installed if the <code>npat</code> flag is -set.</p> <h3 id="dry-run">dry-run</h3> <ul> <li>Default: false</li> @@ -431,9 +432,9 @@ version number, if not already set in package.json.</p> <li>Type: Boolean</li> </ul> <p>Whether or not to output JSON data, rather than the normal output.</p> -<p>This feature is currently experimental, and the output data structures -for many commands is either not implemented in JSON yet, or subject to -change. Only the output from <code>npm ls --json</code> is currently valid.</p> +<p>This feature is currently experimental, and the output data structures for many +commands is either not implemented in JSON yet, or subject to change. Only the +output from <code>npm ls --json</code> and <code>npm search --json</code> are currently valid.</p> <h3 id="key">key</h3> <ul> <li>Default: <code>null</code></li> @@ -522,12 +523,6 @@ combination). Passed to the <code>http</code> <code>Agent</code> used to make th <li>Type: semver or false</li> </ul> <p>The node version to use when checking a package's <code>engines</code> map.</p> -<h3 id="npat">npat</h3> -<ul> -<li>Default: false</li> -<li>Type: Boolean</li> -</ul> -<p>Run tests on installation.</p> <h3 id="onload-script">onload-script</h3> <ul> <li>Default: false</li> @@ -563,7 +558,7 @@ process is not aborted.</p> <li>Type: Boolean</li> </ul> <p>Output parseable results from commands that write to -standard output.</p> +standard output. For <code>npm search</code>, this will be tab-separated table format.</p> <h3 id="prefix">prefix</h3> <ul> <li>Default: see <a href="../files/npm-folders.html">npm-folders(5)</a></li> @@ -685,7 +680,7 @@ set to <code>^1.2.3</code> which allows minor upgrades for that package, but aft patch upgrades.</p> <h3 id="scope">scope</h3> <ul> -<li>Default: ""</li> +<li>Default: the scope of the current project, if any, or ""</li> <li>Type: String</li> </ul> <p>Associate an operation with a scope for a scoped registry. Useful when logging @@ -693,27 +688,40 @@ in to a private registry for the first time: <code>npm login --scope=@organization --registry=registry.organization.com</code>, which will cause <code>@organization</code> to be mapped to the registry for future installation of packages specified according to the pattern <code>@organization/package</code>.</p> -<h3 id="searchopts">searchopts</h3> +<h3 id="scripts-prepend-node-path">scripts-prepend-node-path</h3> +<ul> +<li>Default: "warn-only"</li> +<li>Type: Boolean, <code>"auto"</code> or <code>"warn-only"</code></li> +</ul> +<p>If set to <code>true</code>, add the directory in which the current <code>node</code> executable +resides to the <code>PATH</code> environment variable when running scripts, +even if that means that <code>npm</code> will invoke a different <code>node</code> executable than +the one which it is running.</p> +<p>If set to <code>false</code>, never modify <code>PATH</code> with that.</p> +<p>If set to <code>"warn-only"</code>, never modify <code>PATH</code> but print a warning if <code>npm</code> thinks +that you may want to run it with <code>true</code>, e.g. because the <code>node</code> executable +in the <code>PATH</code> is not the one <code>npm</code> was invoked with.</p> +<p>If set to <code>auto</code>, only add that directory to the <code>PATH</code> environment variable +if the <code>node</code> executable with which <code>npm</code> was invoked and the one that is found +first on the <code>PATH</code> are different.</p> +<h3 id="searchexclude">searchexclude</h3> <ul> <li>Default: ""</li> <li>Type: String</li> </ul> -<p>Space-separated options that are always passed to search.</p> -<h3 id="searchexclude">searchexclude</h3> +<p>Space-separated options that limit the results from search.</p> +<h3 id="searchopts">searchopts</h3> <ul> <li>Default: ""</li> <li>Type: String</li> </ul> -<p>Space-separated options that limit the results from search.</p> -<h3 id="searchsort">searchsort</h3> +<p>Space-separated options that are always passed to search.</p> +<h3 id="searchstaleness">searchstaleness</h3> <ul> -<li>Default: "name"</li> -<li>Type: String</li> -<li>Values: "name", "-name", "date", "-date", "description", -"-description", "keywords", "-keywords"</li> +<li>Default: 900 (15 minutes)</li> +<li>Type: Number</li> </ul> -<p>Indication of which field to sort search results by. Prefix with a <code>-</code> -character to indicate reverse sort.</p> +<p>The age of the cache, in seconds, before another registry request is made.</p> <h3 id="shell">shell</h3> <ul> <li>Default: SHELL environment variable, or "bash" on Posix, or "cmd" on @@ -864,5 +872,5 @@ exit successfully.</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-config — npm@3.10.10</p> +<p id="footer">npm-config — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-developers.html b/deps/npm/html/doc/misc/npm-developers.html index 2c64e124ce..3b04dffacf 100644 --- a/deps/npm/html/doc/misc/npm-developers.html +++ b/deps/npm/html/doc/misc/npm-developers.html @@ -194,5 +194,5 @@ from a fresh checkout.</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-developers — npm@3.10.10</p> +<p id="footer">npm-developers — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-disputes.html b/deps/npm/html/doc/misc/npm-disputes.html index 69a49b6e74..3db7ef27db 100644 --- a/deps/npm/html/doc/misc/npm-disputes.html +++ b/deps/npm/html/doc/misc/npm-disputes.html @@ -10,91 +10,113 @@ <div id="wrapper"> <h1><a href="../misc/npm-disputes.html">npm-disputes</a></h1> <p>Handling Module Name Disputes</p> -<h2 id="synopsis">SYNOPSIS</h2> +<p>This document describes the steps that you should take to resolve module name +disputes with other npm publishers. It also describes special steps you should +take about names you think infringe your trademarks.</p> +<p>This document is a clarification of the acceptable behavior outlined in the +<a href="https://www.npmjs.com/policies/conduct">npm Code of Conduct</a>, and nothing in +this document should be interpreted to contradict any aspect of the npm Code of +Conduct.</p> +<h2 id="tl-dr">TL;DR</h2> <ol> <li>Get the author email with <code>npm owner ls <pkgname></code></li> -<li>Email the author, CC <a href="mailto:support@npmjs.com">support@npmjs.com</a></li> +<li>Email the author, CC <a href="mailto:support@npmjs.com">support@npmjs.com</a></li> <li>After a few weeks, if there's no resolution, we'll sort it out.</li> </ol> <p>Don't squat on package names. Publish code or move out of the way.</p> <h2 id="description">DESCRIPTION</h2> -<p>There sometimes arise cases where a user publishes a module, and then -later, some other user wants to use that name. Here are some common -ways that happens (each of these is based on actual events.)</p> +<p>There sometimes arise cases where a user publishes a module, and then later, +some other user wants to use that name. Here are some common ways that happens +(each of these is based on actual events.)</p> <ol> -<li>Joe writes a JavaScript module <code>foo</code>, which is not node-specific. -Joe doesn't use node at all. Bob wants to use <code>foo</code> in node, so he -wraps it in an npm module. Some time later, Joe starts using node, -and wants to take over management of his program.</li> -<li>Bob writes an npm module <code>foo</code>, and publishes it. Perhaps much -later, Joe finds a bug in <code>foo</code>, and fixes it. He sends a pull -request to Bob, but Bob doesn't have the time to deal with it, -because he has a new job and a new baby and is focused on his new -erlang project, and kind of not involved with node any more. Joe -would like to publish a new <code>foo</code>, but can't, because the name is -taken.</li> -<li>Bob writes a 10-line flow-control library, and calls it <code>foo</code>, and -publishes it to the npm registry. Being a simple little thing, it -never really has to be updated. Joe works for Foo Inc, the makers -of the critically acclaimed and widely-marketed <code>foo</code> JavaScript -toolkit framework. They publish it to npm as <code>foojs</code>, but people are -routinely confused when <code>npm install foo</code> is some different thing.</li> -<li>Bob writes a parser for the widely-known <code>foo</code> file format, because -he needs it for work. Then, he gets a new job, and never updates the -prototype. Later on, Joe writes a much more complete <code>foo</code> parser, -but can't publish, because Bob's <code>foo</code> is in the way.</li> -</ol> -<p>The validity of Joe's claim in each situation can be debated. However, -Joe's appropriate course of action in each case is the same.</p> -<ol> -<li><code>npm owner ls foo</code>. This will tell Joe the email address of the -owner (Bob).</li> -<li>Joe emails Bob, explaining the situation <strong>as respectfully as -possible</strong>, and what he would like to do with the module name. He -adds the npm support staff <a href="mailto:support@npmjs.com">support@npmjs.com</a> to the CC list of -the email. Mention in the email that Bob can run <code>npm owner add -joe foo</code> to add Joe as an owner of the <code>foo</code> package.</li> -<li>After a reasonable amount of time, if Bob has not responded, or if -Bob and Joe can't come to any sort of resolution, email support -<a href="mailto:support@npmjs.com">support@npmjs.com</a> and we'll sort it out. ("Reasonable" is -usually at least 4 weeks, but extra time is allowed around common -holidays.)</li> +<li>Alice writes a JavaScript module <code>foo</code>, which is not node-specific. Alice +doesn't use node at all. Yusuf wants to use <code>foo</code> in node, so he wraps it in +an npm module. Some time later, Alice starts using node, and wants to take +over management of her program.</li> +<li>Yusuf writes an npm module <code>foo</code>, and publishes it. Perhaps much later, Alice +finds a bug in <code>foo</code>, and fixes it. She sends a pull request to Yusuf, but +Yusuf doesn't have the time to deal with it, because he has a new job and a +new baby and is focused on his new Erlang project, and kind of not involved +with node any more. Alice would like to publish a new <code>foo</code>, but can't, +because the name is taken.</li> +<li>Yusuf writes a 10-line flow-control library, and calls it <code>foo</code>, and +publishes it to the npm registry. Being a simple little thing, it never +really has to be updated. Alice works for Foo Inc, the makers of the +critically acclaimed and widely-marketed <code>foo</code> JavaScript toolkit framework. +They publish it to npm as <code>foojs</code>, but people are routinely confused when +<code>npm install</code>foo`` is some different thing.</li> +<li><p>Yusuf writes a parser for the widely-known <code>foo</code> file format, because he +needs it for work. Then, he gets a new job, and never updates the prototype. +Later on, Alice writes a much more complete <code>foo</code> parser, but can't publish, +because Yusuf's <code>foo</code> is in the way.</p> +</li> +<li><p><code>npm owner ls foo</code>. This will tell Alice the email address of the owner +(Yusuf).</p> +</li> +<li>Alice emails Yusuf, explaining the situation <strong>as respectfully as possible</strong>, +and what she would like to do with the module name. She adds the npm support +staff <a href="mailto:support@npmjs.com">support@npmjs.com</a> to the CC list of the email. Mention in the email +that Yusuf can run npm owner <code>add alice foo</code> to add Alice as an owner of the +foo package.</li> +<li>After a reasonable amount of time, if Yusuf has not responded, or if Yusuf +and Alice can't come to any sort of resolution, email support +<a href="mailto:support@npmjs.com">support@npmjs.com</a> and we'll sort it out. ("Reasonable" is usually at least +4 weeks.)</li> </ol> <h2 id="reasoning">REASONING</h2> -<p>In almost every case so far, the parties involved have been able to reach -an amicable resolution without any major intervention. Most people -really do want to be reasonable, and are probably not even aware that -they're in your way.</p> -<p>Module ecosystems are most vibrant and powerful when they are as -self-directed as possible. If an admin one day deletes something you -had worked on, then that is going to make most people quite upset, -regardless of the justification. When humans solve their problems by -talking to other humans with respect, everyone has the chance to end up -feeling good about the interaction.</p> +<p>In almost every case so far, the parties involved have been able to reach an +amicable resolution without any major intervention. Most people really do want +to be reasonable, and are probably not even aware that they're in your way.</p> +<p>Module ecosystems are most vibrant and powerful when they are as self-directed +as possible. If an admin one day deletes something you had worked on, then that +is going to make most people quite upset, regardless of the justification. When +humans solve their problems by talking to other humans with respect, everyone +has the chance to end up feeling good about the interaction.</p> <h2 id="exceptions">EXCEPTIONS</h2> -<p>Some things are not allowed, and will be removed without discussion if -they are brought to the attention of the npm registry admins, including -but not limited to:</p> +<p>Some things are not allowed, and will be removed without discussion if they are +brought to the attention of the npm registry admins, including but not limited +to:</p> <ol> -<li>Malware (that is, a package designed to exploit or harm the machine on -which it is installed).</li> -<li>Violations of copyright or licenses (for example, cloning an -MIT-licensed program, and then removing or changing the copyright and -license statement).</li> +<li>Malware (that is, a package designed to exploit or harm the machine on which +it is installed).</li> +<li>Violations of copyright or licenses (for example, cloning an MIT-licensed +program, and then removing or changing the copyright and license statement).</li> <li>Illegal content.</li> -<li>"Squatting" on a package name that you <em>plan</em> to use, but aren't -actually using. Sorry, I don't care how great the name is, or how -perfect a fit it is for the thing that someday might happen. If -someone wants to use it today, and you're just taking up space with -an empty tarball, you're going to be evicted.</li> -<li>Putting empty packages in the registry. Packages must have SOME -functionality. It can be silly, but it can't be <em>nothing</em>. (See -also: squatting.)</li> -<li>Doing weird things with the registry, like using it as your own -personal application database or otherwise putting non-packagey -things into it.</li> +<li>"Squatting" on a package name that you plan to use, but aren't actually +using. Sorry, I don't care how great the name is, or how perfect a fit it is +for the thing that someday might happen. If someone wants to use it today, +and you're just taking up space with an empty tarball, you're going to be +evicted.</li> +<li>Putting empty packages in the registry. Packages must have SOME +functionality. It can be silly, but it can't be nothing. (See also: +squatting.)</li> +<li>Doing weird things with the registry, like using it as your own personal +application database or otherwise putting non-packagey things into it.</li> +<li>Other things forbidden by the npm +<a href="https://www.npmjs.com/policies/conduct">Code of Conduct</a> such as hateful +language, pornographic content, or harassment.</li> </ol> -<p>If you see bad behavior like this, please report it right away.</p> +<p>If you see bad behavior like this, please report it to <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> right +away. <strong>You are never expected to resolve abusive behavior on your own. We are +here to help.</strong></p> +<h2 id="trademarks">TRADEMARKS</h2> +<p>If you think another npm publisher is infringing your trademark, such as by +using a confusingly similar package name, email <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> with a link to +the package or user account on <a href="https://npmjs.com">https://npmjs.com</a>. Attach a +copy of your trademark registration certificate.</p> +<p>If we see that the package's publisher is intentionally misleading others by +misusing your registered mark without permission, we will transfer the package +name to you. Otherwise, we will contact the package publisher and ask them to +clear up any confusion with changes to their package's <code><a href="../../doc/README.html">README</a></code> file or +metadata.</p> +<h2 id="changes">CHANGES</h2> +<p>This is a living document and may be updated from time to time. Please refer to +the <a href="https://github.com/npm/npm/commits/master/doc/misc/npm-disputes.md">git history for this document</a> +to view the changes.</p> +<h2 id="license">LICENSE</h2> +<p>Copyright (C) npm, Inc., All rights reserved</p> +<p>This document may be reused under a Creative Commons Attribution-ShareAlike +License.</p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../misc/npm-registry.html">npm-registry(7)</a></li> @@ -112,5 +134,5 @@ things into it.</li> <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-disputes — npm@3.10.10</p> +<p id="footer">npm-disputes — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-index.html b/deps/npm/html/doc/misc/npm-index.html index 702e543023..4e590dabe7 100644 --- a/deps/npm/html/doc/misc/npm-index.html +++ b/deps/npm/html/doc/misc/npm-index.html @@ -98,8 +98,6 @@ <p>Start a package</p> <h3 id="npm-stop-1-"><a href="../cli/npm-stop.html">npm-stop(1)</a></h3> <p>Stop a package</p> -<h3 id="npm-tag-1-"><a href="../cli/npm-tag.html">npm-tag(1)</a></h3> -<p>Tag a published version</p> <h3 id="npm-team-1-"><a href="../cli/npm-team.html">npm-team(1)</a></h3> <p>Manage organization teams and team memberships</p> <h3 id="npm-test-1-"><a href="../cli/npm-test.html">npm-test(1)</a></h3> @@ -162,5 +160,5 @@ <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-index — npm@3.10.10</p> +<p id="footer">npm-index — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-orgs.html b/deps/npm/html/doc/misc/npm-orgs.html index 7d5a7cba38..92aa4257e8 100644 --- a/deps/npm/html/doc/misc/npm-orgs.html +++ b/deps/npm/html/doc/misc/npm-orgs.html @@ -86,5 +86,5 @@ <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-orgs — npm@3.10.10</p> +<p id="footer">npm-orgs — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-registry.html b/deps/npm/html/doc/misc/npm-registry.html index b36cfa5bbe..a780c98a45 100644 --- a/deps/npm/html/doc/misc/npm-registry.html +++ b/deps/npm/html/doc/misc/npm-registry.html @@ -25,6 +25,26 @@ available at <a href="https://github.com/npm/npm-registry-couchapp">https://gith <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code>). If no scope is specified, the default registry is used, which is supplied by the <code>registry</code> config parameter. See <code><a href="../cli/npm-config.html">npm-config(1)</a></code>, <code><a href="../files/npmrc.html">npmrc(5)</a></code>, and <code><a href="../misc/npm-config.html">npm-config(7)</a></code> for more on managing npm's configuration.</p> +<h2 id="does-npm-send-any-information-about-me-back-to-the-registry-">Does npm send any information about me back to the registry?</h2> +<p>Yes.</p> +<p>When making requests of the registry npm adds two headers with information +about your environment:</p> +<ul> +<li><code>Npm-Scope</code> – If your project is scoped, this header will contain its +scope. In the future npm hopes to build registry features that use this +information to allow you to customize your experience for your +organization.</li> +<li><code>Npm-In-CI</code> – Set to "true" if npm believes this install is running in a +continous integration environment, "false" otherwise. This is detected by +looking for the following environment variables: <code>CI</code>, <code>TDDIUM</code>, +<code>JENKINS_URL</code>, <code>bamboo.buildKey</code>. If you'd like to learn more you may find +the <a href="https://github.com/npm/npm-registry-client/pull/129">original PR</a> +interesting. +This is used to gather better metrics on how npm is used by humans, versus +build farms.</li> +</ul> +<p>The npm registry does not to correlate the information in these headers with +any authenticated accounts that may be used in the same requests.</p> <h2 id="can-i-run-my-own-private-registry-">Can I run my own private registry?</h2> <p>Yes!</p> <p>The easiest way is to replicate the couch database, and use the same (or @@ -70,5 +90,5 @@ effectively implement the entire CouchDB API anyway.</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-registry — npm@3.10.10</p> +<p id="footer">npm-registry — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-scope.html b/deps/npm/html/doc/misc/npm-scope.html index aed4efe7d1..7295c81fd8 100644 --- a/deps/npm/html/doc/misc/npm-scope.html +++ b/deps/npm/html/doc/misc/npm-scope.html @@ -94,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.10</p> +<p id="footer">npm-scope — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-scripts.html b/deps/npm/html/doc/misc/npm-scripts.html index 172a6cd748..c140ea2152 100644 --- a/deps/npm/html/doc/misc/npm-scripts.html +++ b/deps/npm/html/doc/misc/npm-scripts.html @@ -16,7 +16,13 @@ following scripts:</p> <ul> <li>prepublish: Run BEFORE the package is published. (Also run on local <code>npm -install</code> without any arguments.)</li> +install</code> without any arguments. See below.)</li> +<li>prepare: +Run both BEFORE the package is published, and on local <code>npm +install</code> without any arguments. (See below.) This is run +AFTER <code>prepublish</code>, but BEFORE <code>prepublishOnly</code>.</li> +<li>prepublishOnly: +Run BEFORE the package is published. (See below.)</li> <li>publish, postpublish: Run AFTER the package is published.</li> <li>preinstall: @@ -50,7 +56,25 @@ run-script <stage></code>. <em>Pre</em> and <em>post</em> commands with ma names will be run for those as well (e.g. <code>premyscript</code>, <code>myscript</code>, <code>postmyscript</code>). Scripts from dependencies can be run with `npm explore</p> <p><pkg> -- npm run <stage>`.</p> -<h2 id="common-uses">COMMON USES</h2> +<h2 id="prepublish-and-prepare">PREPUBLISH AND PREPARE</h2> +<h3 id="deprecation-note">DEPRECATION NOTE</h3> +<p>Since <code>npm@1.1.71</code>, the npm CLI has run the <code>prepublish</code> script for both <code>npm +publish</code> and <code>npm install</code>, because it's a convenient way to prepare a package +for use (some common use cases are described in the section below). It has +also turned out to be, in practice, <a href="https://github.com/npm/npm/issues/10074">very +confusing</a>. As of <code>npm@4.0.0</code>, a new +event has been introduced, <code>prepare</code>, that preserves this existing behavior. A +<em>new</em> event, <code>prepublishOnly</code> has been added as a transitional strategy to +allow users to avoid the confusing behavior of existing npm versions and only +run on <code>npm publish</code> (for instance, running the tests one last time to ensure +they're in good shape).</p> +<p><strong>IMPORTANT:</strong> As of <code>npm@5</code>, <code>prepublish</code> will <em>only</em> be run for <code>npm +publish</code>. This will make its behavior identical to <code>prepublishOnly</code>, so +<code>npm@6</code> or later may drop support for the use of <code>prepublishOnly</code>, and then +maybe we can all forget this embarrassing thing ever happened.</p> +<p>See <a href="https://github.com/npm/npm/issues/10074">https://github.com/npm/npm/issues/10074</a> for a much lengthier +justification, with further reading, for this change.</p> +<h3 id="use-cases">USE CASES</h3> <p>If you need to perform operations on your package before it is used, in a way that is not dependent on the operating system or architecture of the target system, use a <code>prepublish</code> script. This includes @@ -213,5 +237,5 @@ scripts is for compilation which must be done on the target architecture.</li> <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-scripts — npm@3.10.10</p> +<p id="footer">npm-scripts — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/removing-npm.html b/deps/npm/html/doc/misc/removing-npm.html index 6b2f30a72b..63d0648844 100644 --- a/deps/npm/html/doc/misc/removing-npm.html +++ b/deps/npm/html/doc/misc/removing-npm.html @@ -57,5 +57,5 @@ modules. To track those down, you can do the following:</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">removing-npm — npm@3.10.10</p> +<p id="footer">removing-npm — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/semver.html b/deps/npm/html/doc/misc/semver.html index 7e053f6228..2ae0288f99 100644 --- a/deps/npm/html/doc/misc/semver.html +++ b/deps/npm/html/doc/misc/semver.html @@ -325,5 +325,5 @@ range, use the <code>satisfies(version, range)</code> function.</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">semver — npm@3.10.10</p> +<p id="footer">semver — npm@4.0.5</p> |