diff options
| author | Rebecca Turner <me@re-becca.org> | 2016-01-28 18:11:35 -0800 |
|---|---|---|
| committer | Jeremiah Senkpiel <fishrock123@rocketmail.com> | 2016-02-01 10:43:34 -0500 |
| commit | 76cb81b354de8447898427619c66c86c59b22b3d (patch) | |
| tree | 0c0826bed77086fb38cda8dc680d4fb10d2cff25 /deps/npm/html/doc | |
| parent | d5d301f3032a0723f5a29cfbe0d95ac4ad205d42 (diff) | |
| download | node-new-76cb81b354de8447898427619c66c86c59b22b3d.tar.gz | |
deps: upgrade npm to 3.6.0
PR-URL: https://github.com/nodejs/node/pull/4958
Reviewed-By: Myles Borins <mborins@us.ibm.com>
Reviewed-By: Kat Marchán <kzm@sykosomatic.org>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Diffstat (limited to 'deps/npm/html/doc')
70 files changed, 322 insertions, 529 deletions
diff --git a/deps/npm/html/doc/README.html b/deps/npm/html/doc/README.html index 7d191393d4..6160d3b09d 100644 --- a/deps/npm/html/doc/README.html +++ b/deps/npm/html/doc/README.html @@ -18,6 +18,14 @@ <p><strong>You need node v0.8 or higher to run this program.</strong></p> <p>To install an old <strong>and unsupported</strong> version of npm that works on node 0.3 and prior, clone the git repo and dig through the old tags and branches.</p> +<p><strong>npm is configured to use npm, Inc.'s public package registry at +<a href="https://registry.npmjs.org">https://registry.npmjs.org</a> by default.</strong></p> +<p>You can configure npm to use any compatible registry you +like, and even run your own registry. Check out the <a href="https://docs.npmjs.com/misc/registry">doc on +registries</a>.</p> +<p>Use of someone else's registry may be governed by terms of use. The +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> <h3 id="windows-computers">Windows Computers</h3> @@ -84,76 +92,12 @@ npm config get globalconfig # defaults to /usr/local/etc/npmrc must remove them yourself manually if you want them gone. Note that this means that future npm installs will not remember the settings that you have chosen.</p> -<h2 id="using-npm-programmatically">Using npm Programmatically</h2> -<p>Although npm can be used programmatically, its API is meant for use by the CLI -<em>only</em>, and no guarantees are made regarding its fitness for any other purpose. -If you want to use npm to reliably perform some task, the safest thing to do is -to invoke the desired <code>npm</code> command with appropriate arguments.</p> -<p>The semantic version of npm refers to the CLI itself, rather than the -underlying API. <em>The internal API is not guaranteed to remain stable even when -npm's version indicates no breaking changes have been made according to -semver.</em></p> -<p>If you <em>still</em> would like to use npm programmatically, it's <em>possible</em>. The API -isn't very well documented, but it <em>is</em> rather simple.</p> -<p>Eventually, npm will be just a thin CLI wrapper around the modules that it -depends on, but for now, there are some things that only the CLI can do. You -should try using one of npm's dependencies first, and only use the API if what -you're trying to do is only supported by npm itself.</p> -<pre><code class="lang-javascript">var npm = require("npm") -npm.load(myConfigObject, function (er) { - if (er) return handlError(er) - npm.commands.install(["some", "args"], function (er, data) { - if (er) return commandFailed(er) - // command succeeded, and data might have some info - }) - npm.registry.log.on("log", function (message) { .... }) -}) -</code></pre> -<p>The <code>load</code> function takes an object hash of the command-line configs. -The various <code>npm.commands.<cmd></code> functions take an <strong>array</strong> of -positional argument <strong>strings</strong>. The last argument to any -<code>npm.commands.<cmd></code> function is a callback. Some commands take other -optional arguments. Read the source.</p> -<p>You cannot set configs individually for any single npm function at this -time. Since <code>npm</code> is a singleton, any call to <code>npm.config.set</code> will -change the value for <em>all</em> npm commands in that process.</p> -<p>See <code>./bin/npm-cli.js</code> for an example of pulling config values off of the -command line arguments using nopt. You may also want to check out <code>npm -help config</code> to learn about all the options you can set there.</p> <h2 id="more-docs">More Docs</h2> <p>Check out the <a href="https://docs.npmjs.com/">docs</a>, especially the <a href="https://docs.npmjs.com/misc/faq">faq</a>.</p> <p>You can use the <code>npm help</code> command to read any of them.</p> <p>If you're a developer, and you want to use npm to publish your program, you should <a href="https://docs.npmjs.com/misc/developers">read this</a></p> -<h2 id="legal-stuff">Legal Stuff</h2> -<p>"npm" and "The npm Registry" are owned by npm, Inc. -All rights reserved. See the included LICENSE file for more details.</p> -<p>"Node.js" and "node" are trademarks owned by Joyent, Inc.</p> -<p>Modules published on the npm registry are not officially endorsed by -npm, Inc. or the Node.js project.</p> -<p>Data published to the npm registry is not part of npm itself, and is -the sole property of the publisher. While every effort is made to -ensure accountability, there is absolutely no guarantee, warranty, or -assertion expressed or implied as to the quality, fitness for a -specific purpose, or lack of malice in any given npm package.</p> -<p>If you have a complaint about a package in the public npm registry, -and cannot <a href="https://docs.npmjs.com/misc/disputes">resolve it with the package -owner</a>, please email -<a href="mailto:support@npmjs.com">support@npmjs.com</a> and explain the situation.</p> -<p>Any data published to The npm Registry (including user account -information) may be removed or modified at the sole discretion of the -npm server administrators.</p> -<h3 id="in-plainer-english">In plainer English</h3> -<p>npm is the property of npm, Inc.</p> -<p>If you publish something, it's yours, and you are solely accountable -for it.</p> -<p>If other people publish something, it's theirs.</p> -<p>Users can publish Bad Stuff. It will be removed promptly if reported. -But there is no vetting process for published modules, and you use -them at your own risk. Please inspect the source.</p> -<p>If you publish Bad Stuff, we may delete it from the registry, or even -ban your account in extreme cases. So don't do that.</p> <h2 id="bugs">BUGS</h2> <p>When you find issues, please report them:</p> <ul> @@ -183,5 +127,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.3.12</p> +<p id="footer"><a href="../doc/README.html">README</a> — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-access.html b/deps/npm/html/doc/cli/npm-access.html index 001fe175cd..425cf63744 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.3.12</p> +<p id="footer">npm-access — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-adduser.html b/deps/npm/html/doc/cli/npm-adduser.html index d3d9c2e618..9e06fc99e1 100644 --- a/deps/npm/html/doc/cli/npm-adduser.html +++ b/deps/npm/html/doc/cli/npm-adduser.html @@ -26,7 +26,7 @@ your existing record.</p> <p><code>npm login</code> is an alias to <code>adduser</code> and behaves exactly the same way.</p> <h2 id="configuration">CONFIGURATION</h2> <h3 id="registry">registry</h3> -<p>Default: <a href="http://registry.npmjs.org/">http://registry.npmjs.org/</a></p> +<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> <h3 id="scope">scope</h3> @@ -68,5 +68,5 @@ precedence 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.3.12</p> +<p id="footer">npm-adduser — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-bin.html b/deps/npm/html/doc/cli/npm-bin.html index c7c39e06c2..165e0e29fd 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.3.12</p> +<p id="footer">npm-bin — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-bugs.html b/deps/npm/html/doc/cli/npm-bugs.html index 862cd8ee64..dc9c7cd8e6 100644 --- a/deps/npm/html/doc/cli/npm-bugs.html +++ b/deps/npm/html/doc/cli/npm-bugs.html @@ -53,5 +53,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.3.12</p> +<p id="footer">npm-bugs — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-build.html b/deps/npm/html/doc/cli/npm-build.html index b630367628..3ec57f9184 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.3.12</p> +<p id="footer">npm-build — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-bundle.html b/deps/npm/html/doc/cli/npm-bundle.html index 8d2e9e4b39..2247408a55 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.3.12</p> +<p id="footer">npm-bundle — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-cache.html b/deps/npm/html/doc/cli/npm-cache.html index 989c06bdce..bf766ef426 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.3.12</p> +<p id="footer">npm-cache — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-completion.html b/deps/npm/html/doc/cli/npm-completion.html index 150957ba65..84cde0e6bb 100644 --- a/deps/npm/html/doc/cli/npm-completion.html +++ b/deps/npm/html/doc/cli/npm-completion.html @@ -44,5 +44,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.3.12</p> +<p id="footer">npm-completion — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-config.html b/deps/npm/html/doc/cli/npm-config.html index b38e1dd29a..c7d2b1ce7e 100644 --- a/deps/npm/html/doc/cli/npm-config.html +++ b/deps/npm/html/doc/cli/npm-config.html @@ -65,5 +65,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.3.12</p> +<p id="footer">npm-config — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-dedupe.html b/deps/npm/html/doc/cli/npm-dedupe.html index 1e16100695..2f03cd836d 100644 --- a/deps/npm/html/doc/cli/npm-dedupe.html +++ b/deps/npm/html/doc/cli/npm-dedupe.html @@ -11,8 +11,8 @@ <h1><a href="../cli/npm-dedupe.html">npm-dedupe</a></h1> <p>Reduce duplication</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm dedupe [package names...] -npm ddp [package names...] +<pre><code>npm dedupe +npm ddp </code></pre><h2 id="description">DESCRIPTION</h2> <p>Searches the local package tree and attempts to simplify the overall structure by moving dependencies further up the tree, where they can @@ -59,5 +59,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.3.12</p> +<p id="footer">npm-dedupe — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-deprecate.html b/deps/npm/html/doc/cli/npm-deprecate.html index 22492af06e..c1d82e4ab4 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.3.12</p> +<p id="footer">npm-deprecate — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-dist-tag.html b/deps/npm/html/doc/cli/npm-dist-tag.html index 49d06f74a3..d066b8dcd7 100644 --- a/deps/npm/html/doc/cli/npm-dist-tag.html +++ b/deps/npm/html/doc/cli/npm-dist-tag.html @@ -35,14 +35,23 @@ of using a specific version number:</p> </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 sets the "latest" tag to the published version unless the +<p>Publishing a package sets the <code>latest</code> tag to the published version unless the <code>--tag</code> option is used. For example, <code>npm publish --tag=beta</code>.</p> +<p>By default, <code>npm install <pkg></code> (without any <code>@<version></code> or <code>@<tag></code> +specifier) installs the <code>latest</code> tag.</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> +<p>Tags can be used to provide an alias instead of version numbers.</p> +<p>For example, a project might choose to have multiple streams of development +and use a different tag for each stream, +e.g., <code>stable</code>, <code>beta</code>, <code>dev</code>, <code>canary</code>.</p> +<p>By default, the <code>latest</code> tag is used by npm to identify the current version of +a package, and <code>npm install <pkg></code> (without any <code>@<version></code> or <code>@<tag></code> +specifier) installs the <code>latest</code> tag. Typically, projects only use the <code>latest</code> +tag for stable release versions, and use other tags for unstable versions such +as prereleases.</p> +<p>The <code>next</code> tag is used by some projects to identify the upcoming version.</p> +<p>By default, other than <code>latest</code>, no tag has any special significance to npm +itself.</p> <h2 id="caveats">CAVEATS</h2> <p>This command used to be known as <code>npm tag</code>, which only created new tags, and so had a different syntax.</p> @@ -62,7 +71,6 @@ begin with a number or the letter <code>v</code>.</p> <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="../api/npm-tag.html">npm-tag(3)</a></li> <li><a href="../files/npmrc.html">npmrc(5)</a></li> </ul> @@ -77,5 +85,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.3.12</p> +<p id="footer">npm-dist-tag — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-docs.html b/deps/npm/html/doc/cli/npm-docs.html index 763d17fef4..e783d27864 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.3.12</p> +<p id="footer">npm-docs — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-edit.html b/deps/npm/html/doc/cli/npm-edit.html index 47581a3260..18b2d3ef5c 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.3.12</p> +<p id="footer">npm-edit — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-explore.html b/deps/npm/html/doc/cli/npm-explore.html index d585315aa0..5773991f8c 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.3.12</p> +<p id="footer">npm-explore — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-help-search.html b/deps/npm/html/doc/cli/npm-help-search.html index 3d1205c0c3..6d27bf377a 100644 --- a/deps/npm/html/doc/cli/npm-help-search.html +++ b/deps/npm/html/doc/cli/npm-help-search.html @@ -46,5 +46,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.3.12</p> +<p id="footer">npm-help-search — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-help.html b/deps/npm/html/doc/cli/npm-help.html index f7cbfd7c22..a104ea129a 100644 --- a/deps/npm/html/doc/cli/npm-help.html +++ b/deps/npm/html/doc/cli/npm-help.html @@ -51,5 +51,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.3.12</p> +<p id="footer">npm-help — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-init.html b/deps/npm/html/doc/cli/npm-init.html index b23c3b9e5b..84b40ea176 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.3.12</p> +<p id="footer">npm-init — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-install-test.html b/deps/npm/html/doc/cli/npm-install-test.html new file mode 100644 index 0000000000..5d618fc18e --- /dev/null +++ b/deps/npm/html/doc/cli/npm-install-test.html @@ -0,0 +1,45 @@ +<!doctype html> +<html> + <title>npm-install-test</title> + <meta http-equiv="content-type" value="text/html;utf-8"> + <link rel="stylesheet" type="text/css" href="../../static/style.css"> + <link rel="canonical" href="https://www.npmjs.org/doc/cli/npm-install-test.html"> + <script async=true src="../../static/toc.js"></script> + + <body> + <div id="wrapper"> + +<h1>npm <a href="../cli/install-test.html">install-test</a></h1> <p>Install package(s) and run tests</p> +<h2 id="synopsis">SYNOPSIS</h2> +<pre><code>npm install-test (with no args, in package dir) +npm install-test [<@scope>/]<name> +npm install-test [<@scope>/]<name>@<tag> +npm install-test [<@scope>/]<name>@<version> +npm install-test [<@scope>/]<name>@<version range> +npm install-test <tarball file> +npm install-test <tarball url> +npm install-test <folder> + +alias: npm it +common options: [--save|--save-dev|--save-optional] [--save-exact] [--dry-run] +</code></pre><h2 id="description">DESCRIPTION</h2> +<p>This command runs an <code>npm install</code> followed immediately by an <code>npm test</code>. It +takes exactly the same arguments as <code>npm install</code>.</p> +<h2 id="see-also">SEE ALSO</h2> +<ul> +<li><a href="../cli/npm-install.html">npm-install(1)</a></li> +<li><a href="../cli/npm-test.html">npm-test(1)</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-install-test — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-install.html b/deps/npm/html/doc/cli/npm-install.html index 52ffa24fb4..56f1525306 100644 --- a/deps/npm/html/doc/cli/npm-install.html +++ b/deps/npm/html/doc/cli/npm-install.html @@ -28,11 +28,11 @@ package has a shrinkwrap file, the installation of dependencies will be driven by that. See <a href="../cli/npm-shrinkwrap.html">npm-shrinkwrap(1)</a>.</p> <p>A <code>package</code> is:</p> <ul> -<li>a) a folder containing a program described by a package.json file</li> +<li>a) a folder containing a program described by a <code><a href="../files/package.json.html">package.json(5)</a></code> file</li> <li>b) a gzipped tarball containing (a)</li> <li>c) a url that resolves to (b)</li> <li>d) a <code><name>@<version></code> that is published on the registry (see <code><a href="../misc/npm-registry.html">npm-registry(7)</a></code>) with (c)</li> -<li>e) a <code><name>@<tag></code> that points to (d)</li> +<li>e) a <code><name>@<tag></code> (see <code><a href="../cli/npm-dist-tag.html">npm-dist-tag(1)</a></code>) that points to (d)</li> <li>f) a <code><name></code> that has a "latest" tag satisfying (e)</li> <li>g) a <code><git remote url></code> that resolves to (a)</li> </ul> @@ -46,8 +46,9 @@ after packing it up into a tarball (b).</p> <p> In global mode (ie, with <code>-g</code> or <code>--global</code> appended to the command), it installs the current package context (ie, the current working directory) as a global package.</p> -<p> By default, <code>npm install</code> will install all modules listed as dependencies. - With the <code>--production</code> flag (or when the <code>NODE_ENV</code> environment variable +<p> By default, <code>npm install</code> will install all modules listed as dependencies + in <code><a href="../files/package.json.html">package.json(5)</a></code>.</p> +<p> With the <code>--production</code> flag (or when the <code>NODE_ENV</code> environment variable is set to <code>production</code>), npm will not install modules listed in <code>devDependencies</code>.</p> </li> @@ -69,7 +70,7 @@ after packing it up into a tarball (b).</p> </code></pre></li> <li><p><code>npm install [<@scope>/]<name> [-S|--save|-D|--save-dev|-O|--save-optional]</code>:</p> <p> Do a <code><name>@<tag></code> install, where <code><tag></code> is the "tag" config. (See - <code><a href="../misc/npm-config.html">npm-config(7)</a></code>.)</p> + <code><a href="../misc/npm-config.html">npm-config(7)</a></code>. The config's default value is <code>latest</code>.)</p> <p> In most cases, this will install the latest version of the module published on npm.</p> <p> Example:</p> @@ -206,6 +207,14 @@ local copy exists on disk.</p> <pre><code>npm install sax --force </code></pre><p>The <code>-g</code> or <code>--global</code> argument will cause npm to install the package globally rather than locally. See <code><a href="../files/npm-folders.html">npm-folders(5)</a></code>.</p> +<p>The <code>--global-style</code> argument will cause npm to install the package into +your local <code>node_modules</code> folder with the same layout it uses with the +global <code>node_modules</code> folder. Only your direct dependencies will show in +<code>node_modules</code> and everything they depend on will be flattened in their +<code>node_modules</code> folders. This obviously will elminate some deduping.</p> +<p>The <code>--legacy-bundling</code> argument will cause npm to install the package such +that versions of npm prior to 1.4, such as the one included with node 0.8, +can install the package. This eliminates all automatic deduping.</p> <p>The <code>--link</code> argument will cause npm to link global installs into the local space in some cases.</p> <p>The <code>--no-bin-links</code> argument will prevent npm from creating symlinks for @@ -280,8 +289,9 @@ affects a real use-case, it will be investigated.</p> <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-rm.html">npm-rm(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> </ul> </div> @@ -295,5 +305,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.3.12</p> +<p id="footer">npm-install — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-link.html b/deps/npm/html/doc/cli/npm-link.html index 16505c4331..63122bc890 100644 --- a/deps/npm/html/doc/cli/npm-link.html +++ b/deps/npm/html/doc/cli/npm-link.html @@ -73,5 +73,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.3.12</p> +<p id="footer">npm-link — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-logout.html b/deps/npm/html/doc/cli/npm-logout.html index 27f70f529e..7a496c4e27 100644 --- a/deps/npm/html/doc/cli/npm-logout.html +++ b/deps/npm/html/doc/cli/npm-logout.html @@ -23,7 +23,7 @@ the current environment.</p> connected to that scope, if set.</p> <h2 id="configuration">CONFIGURATION</h2> <h3 id="registry">registry</h3> -<p>Default: <a href="http://registry.npmjs.org/">http://registry.npmjs.org/</a></p> +<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, it takes precedence.</p> <h3 id="scope">scope</h3> @@ -55,5 +55,5 @@ that registry at the same 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-logout — npm@3.3.12</p> +<p id="footer">npm-logout — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-ls.html b/deps/npm/html/doc/cli/npm-ls.html index 2fec3f055a..8dcbe52bc8 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.3.12 /path/to/npm +<pre><code>npm@3.6.0 /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.3.12</p> +<p id="footer">npm-ls — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-outdated.html b/deps/npm/html/doc/cli/npm-outdated.html index 69513a8d7b..0c007aa4b1 100644 --- a/deps/npm/html/doc/cli/npm-outdated.html +++ b/deps/npm/html/doc/cli/npm-outdated.html @@ -15,9 +15,56 @@ </code></pre><h2 id="description">DESCRIPTION</h2> <p>This command will check the registry to see if any (or, specific) installed packages are currently outdated.</p> -<p>The resulting field 'wanted' shows the latest version according to the -version specified in the package.json, the field 'latest' the very latest -version of the package.</p> +<p>In the output:</p> +<ul> +<li><code>wanted</code> is the maximum version of the package that satisfies the semver +range specified in <code>package.json</code>. If there's no available semver range (i.e. +you're running <code>npm outdated --global</code>, or the package isn't included in +<code>package.json</code>), then <code>wanted</code> shows the currently-installed version.</li> +<li><code>latest</code> is the version of the package tagged as latest in the registry. +Running <code>npm publish</code> with no special configuration will publish the package +with a dist-tag of <code>latest</code>. This may or may not be the maximum version of +the package, or the most-recently published version of the package, depending +on how the package's developer manages the latest <a href="../cli/dist-tag.html">dist-tag(1)</a>.</li> +<li><code>location</code> is where in the dependency tree the package is located. Note that +<code>npm outdated</code> defaults to a depth of 0, so unless you override that, you'll +always be seeing only top-level dependencies that are outdated.</li> +<li><code>package type</code> (when using <code>--long</code> / <code>-l</code>) tells you whether this package is +a <code>dependency</code> or a <code>devDependency</code>. Packages not included in <code>package.json</code> +are always marked <code>dependencies</code>.</li> +</ul> +<h3 id="an-example">An example</h3> +<pre><code>$ npm outdated +Package Current Wanted Latest Location +glob 5.0.15 5.0.15 6.0.1 test-outdated-output +nothingness 0.0.3 git git test-outdated-output +npm 3.5.1 3.5.2 3.5.1 test-outdated-output +local-dev 0.0.3 linked linked test-outdated-output +once 1.3.2 1.3.3 1.3.3 test-outdated-output +</code></pre><p>With these <code>dependencies</code>:</p> +<pre><code class="lang-json">{ + "glob": "^5.0.15", + "nothingness": "github:othiym23/nothingness#master", + "npm": "^3.5.1", + "once": "^1.3.1" +} +</code></pre> +<p>A few things to note:</p> +<ul> +<li><code>glob</code> requires <code>^5</code>, which prevents npm from installing <code>glob@6</code>, which is +outside the semver range.</li> +<li>Git dependencies will always be reinstalled, because of how they're specified. +The installed committish might satisfy the dependency specifier (if it's +something immutable, like a commit SHA), or it might not, so <code>npm outdated</code> and +<code>npm update</code> have to fetch Git repos to check. This is why currently doing a +reinstall of a Git dependency always forces a new clone and install.</li> +<li><code>npm@3.5.2</code> is marked as "wanted", but "latest" is <code>npm@3.5.1</code> because npm +uses dist-tags to manage its <code>latest</code> and <code>next</code> release channels. <code>npm update</code> +will install the <em>newest</em> version, but <code>npm install npm</code> (with no semver range) +will install whatever's tagged as <code>latest</code>.</li> +<li><code>once</code> is just plain out of date. Reinstalling <code>node_modules</code> from scratch or +running <code>npm update</code> will bring it up to spec.</li> +</ul> <h2 id="configuration">CONFIGURATION</h2> <h3 id="json">json</h3> <ul> @@ -46,12 +93,14 @@ version of the package.</p> project.</p> <h3 id="depth">depth</h3> <ul> +<li>Default: 0</li> <li>Type: Int</li> </ul> <p>Max depth for checking dependency tree.</p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../cli/npm-update.html">npm-update(1)</a></li> +<li><a href="../cli/npm-dist-tag.html">npm-dist-tag(1)</a></li> <li><a href="../misc/npm-registry.html">npm-registry(7)</a></li> <li><a href="../files/npm-folders.html">npm-folders(5)</a></li> </ul> @@ -67,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.3.12</p> +<p id="footer">npm-outdated — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-owner.html b/deps/npm/html/doc/cli/npm-owner.html index 99c485c7d9..ac7cef923a 100644 --- a/deps/npm/html/doc/cli/npm-owner.html +++ b/deps/npm/html/doc/cli/npm-owner.html @@ -49,5 +49,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.3.12</p> +<p id="footer">npm-owner — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-pack.html b/deps/npm/html/doc/cli/npm-pack.html index b35b2c40f8..1970de1052 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.3.12</p> +<p id="footer">npm-pack — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-ping.html b/deps/npm/html/doc/cli/npm-ping.html index c5a8fb663b..7ebf981a2c 100644 --- a/deps/npm/html/doc/cli/npm-ping.html +++ b/deps/npm/html/doc/cli/npm-ping.html @@ -32,4 +32,4 @@ <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.3.12</p> +<p id="footer">npm-ping — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-prefix.html b/deps/npm/html/doc/cli/npm-prefix.html index 9111d20c76..c12a62a9ed 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.3.12</p> +<p id="footer">npm-prefix — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-prune.html b/deps/npm/html/doc/cli/npm-prune.html index 43010bc3c2..dcd15a325c 100644 --- a/deps/npm/html/doc/cli/npm-prune.html +++ b/deps/npm/html/doc/cli/npm-prune.html @@ -24,7 +24,7 @@ specified in your <code>devDependencies</code>. Setting <code>--production=false negate <code>NODE_ENV</code> being set to <code>production</code>.</p> <h2 id="see-also">SEE ALSO</h2> <ul> -<li><a href="../cli/npm-rm.html">npm-rm(1)</a></li> +<li><a href="../cli/npm-uninstall.html">npm-uninstall(1)</a></li> <li><a href="../files/npm-folders.html">npm-folders(5)</a></li> <li><a href="../cli/npm-ls.html">npm-ls(1)</a></li> </ul> @@ -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.3.12</p> +<p id="footer">npm-prune — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-publish.html b/deps/npm/html/doc/cli/npm-publish.html index c2d8b0815a..988de864b5 100644 --- a/deps/npm/html/doc/cli/npm-publish.html +++ b/deps/npm/html/doc/cli/npm-publish.html @@ -16,9 +16,12 @@ Publishes '.' if no argument supplied Sets tag 'latest' if no --tag specified </code></pre><h2 id="description">DESCRIPTION</h2> -<p>Publishes a package to the registry so that it can be installed by name. See -<code><a href="../misc/npm-developers.html">npm-developers(7)</a></code> for details on what's included in the published package, as -well as details on how the package is built.</p> +<p>Publishes a package to the registry so that it can be installed by name. All +files in the package directory are included if no local <code>.gitignore</code> or +<code>.npmignore</code> file exists. If both files exist and a file is ignored by +<code>.gitignore</code> but not by <code>.npmignore</code> then it will be included. See +<code><a href="../misc/npm-developers.html">npm-developers(7)</a></code> for full details on what's included in the published +package, as well as details on how the package is built.</p> <p>By default npm will publish to the public registry. This can be overridden by specifying a different default registry or using a <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code> in the name (see <code><a href="../files/package.json.html">package.json(5)</a></code>).</p> @@ -33,7 +36,8 @@ with a package.json file inside.</p> <li><p><code>[--tag <tag>]</code> Registers the published package with the given tag, such that <code>npm install <name>@<tag></code> will install this version. By default, <code>npm publish</code> updates -and <code>npm install</code> installs the <code>latest</code> tag.</p> +and <code>npm install</code> installs the <code>latest</code> tag. See <code><a href="../cli/npm-dist-tag.html">npm-dist-tag(1)</a></code> for +details about tags.</p> </li> <li><p><code>[--access <public|restricted>]</code> Tells the registry whether this package should be published as public or @@ -68,5 +72,5 @@ it is removed with <a href="../cli/npm-unpublish.html">npm-unpublish(1)</a>.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-publish — npm@3.3.12</p> +<p id="footer">npm-publish — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-rebuild.html b/deps/npm/html/doc/cli/npm-rebuild.html index 9fdabf5747..da082d5123 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.3.12</p> +<p id="footer">npm-rebuild — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-repo.html b/deps/npm/html/doc/cli/npm-repo.html index bf94fde6a5..d2209b214f 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.3.12</p> +<p id="footer">npm-repo — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-restart.html b/deps/npm/html/doc/cli/npm-restart.html index eb7bf47c5a..42ba7f32d8 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.3.12</p> +<p id="footer">npm-restart — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-root.html b/deps/npm/html/doc/cli/npm-root.html index eaf93c0ac6..8466b90c0c 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.3.12</p> +<p id="footer">npm-root — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-run-script.html b/deps/npm/html/doc/cli/npm-run-script.html index 487c086adc..60d0619557 100644 --- a/deps/npm/html/doc/cli/npm-run-script.html +++ b/deps/npm/html/doc/cli/npm-run-script.html @@ -38,6 +38,8 @@ prefix. For example, if there is a <code>devDependency</code> on <code>tap</code 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>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> <ul> <li><a href="../misc/npm-scripts.html">npm-scripts(7)</a></li> @@ -58,5 +60,5 @@ you should write:</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-run-script — npm@3.3.12</p> +<p id="footer">npm-run-script — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-search.html b/deps/npm/html/doc/cli/npm-search.html index 6c31f1b60c..b68458788f 100644 --- a/deps/npm/html/doc/cli/npm-search.html +++ b/deps/npm/html/doc/cli/npm-search.html @@ -49,5 +49,5 @@ fall on multiple lines.</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-search — npm@3.3.12</p> +<p id="footer">npm-search — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-shrinkwrap.html b/deps/npm/html/doc/cli/npm-shrinkwrap.html index ab72eb0d71..8b550e04d4 100644 --- a/deps/npm/html/doc/cli/npm-shrinkwrap.html +++ b/deps/npm/html/doc/cli/npm-shrinkwrap.html @@ -169,5 +169,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.3.12</p> +<p id="footer">npm-shrinkwrap — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-star.html b/deps/npm/html/doc/cli/npm-star.html index be7f542964..0fd7720fa4 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.3.12</p> +<p id="footer">npm-star — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-stars.html b/deps/npm/html/doc/cli/npm-stars.html index eac253ff8e..ed39de1465 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.3.12</p> +<p id="footer">npm-stars — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-start.html b/deps/npm/html/doc/cli/npm-start.html index 410364f5fa..0d4e6ed111 100644 --- a/deps/npm/html/doc/cli/npm-start.html +++ b/deps/npm/html/doc/cli/npm-start.html @@ -13,7 +13,12 @@ <h2 id="synopsis">SYNOPSIS</h2> <pre><code>npm start [-- <args>] </code></pre><h2 id="description">DESCRIPTION</h2> -<p>This runs a package's "start" script, if one was provided.</p> +<p>This runs an arbitrary command specified in the package's <code>"start"</code> property of +its <code>"scripts"</code> object. If no <code>"start"</code> property is specified on the +<code>"scripts"</code> object, it will run <code>node server.js</code>.</p> +<p>As of <a href="http://blog.npmjs.org/post/98131109725/npm-2-0-0"><code>npm@2.0.0</code></a>, you can +use custom arguments when executing scripts. Refer to <a href="../cli/npm-run-script.html">npm-run-script(1)</a> for +more details.</p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../cli/npm-run-script.html">npm-run-script(1)</a></li> @@ -34,5 +39,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-start — npm@3.3.12</p> +<p id="footer">npm-start — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-stop.html b/deps/npm/html/doc/cli/npm-stop.html index 2c99d66465..1b614a25f2 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.3.12</p> +<p id="footer">npm-stop — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-tag.html b/deps/npm/html/doc/cli/npm-tag.html index 1bbecd6c69..e2291046fa 100644 --- a/deps/npm/html/doc/cli/npm-tag.html +++ b/deps/npm/html/doc/cli/npm-tag.html @@ -63,5 +63,5 @@ that do not 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-tag — npm@3.3.12</p> +<p id="footer">npm-tag — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-team.html b/deps/npm/html/doc/cli/npm-team.html index dab0a0e1d1..64ac7cf75d 100644 --- a/deps/npm/html/doc/cli/npm-team.html +++ b/deps/npm/html/doc/cli/npm-team.html @@ -26,7 +26,7 @@ handle permissions for packages.</p> <p>Teams must always be fully qualified with the organization/scope they belong to when operating on them, separated by a colon (<code>:</code>). That is, if you have a <code>developers</code> team on a <code>foo</code> organization, you must always refer to that team as -<code>developers:foo</code> in these commands.</p> +<code>foo:developers</code> in these commands.</p> <ul> <li><p>create / destroy: Create a new team, or destroy an existing one.</p> @@ -67,4 +67,4 @@ 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.3.12</p> +<p id="footer">npm-team — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-test.html b/deps/npm/html/doc/cli/npm-test.html index 206de736c5..5f41acd1c3 100644 --- a/deps/npm/html/doc/cli/npm-test.html +++ b/deps/npm/html/doc/cli/npm-test.html @@ -37,5 +37,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.3.12</p> +<p id="footer">npm-test — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-uninstall.html b/deps/npm/html/doc/cli/npm-uninstall.html index 93fe4810f2..715c96954f 100644 --- a/deps/npm/html/doc/cli/npm-uninstall.html +++ b/deps/npm/html/doc/cli/npm-uninstall.html @@ -9,7 +9,7 @@ <body> <div id="wrapper"> -<h1><a href="../cli/npm-rm.html">npm-rm</a></h1> <p>Remove a package</p> +<h1><a href="../cli/npm-uninstall.html">npm-uninstall</a></h1> <p>Remove a package</p> <h2 id="synopsis">SYNOPSIS</h2> <pre><code>npm uninstall [<@scope>/]<pkg>[@<version>]... [-S|--save|-D|--save-dev|-O|--save-optional] @@ -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.3.12</p> +<p id="footer">npm-uninstall — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-unpublish.html b/deps/npm/html/doc/cli/npm-unpublish.html index da50613ed6..4b6d4daddd 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.3.12</p> +<p id="footer">npm-unpublish — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-update.html b/deps/npm/html/doc/cli/npm-update.html index fe4e3c178f..fb5333422e 100644 --- a/deps/npm/html/doc/cli/npm-update.html +++ b/deps/npm/html/doc/cli/npm-update.html @@ -24,7 +24,7 @@ packages.</p> or local) will be updated.</p> <p>As of <code>npm@2.6.1</code>, the <code>npm update</code> will only inspect top-level packages. Prior versions of <code>npm</code> would also recursively inspect all dependencies. -To get the old behavior, use <code>npm --depth 9999 update</code>, but be warned that +To get the old behavior, use <code>npm --depth Infinity update</code>, but be warned that simultaneous asynchronous update of all packages, including <code>npm</code> itself and packages that <code>npm</code> depends on, often causes problems up to and including the uninstallation of <code>npm</code> itself.</p> @@ -120,5 +120,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.3.12</p> +<p id="footer">npm-update — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-version.html b/deps/npm/html/doc/cli/npm-version.html index bc3cf3b5d6..5e9a7ee326 100644 --- a/deps/npm/html/doc/cli/npm-version.html +++ b/deps/npm/html/doc/cli/npm-version.html @@ -11,7 +11,7 @@ <h1><a href="../cli/npm-version.html">npm-version</a></h1> <p>Bump a package version</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease] +<pre><code>npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease | from-git] 'npm [-v | --version]' to print npm version 'npm view <pkg> version' to view a package's published version @@ -19,10 +19,11 @@ </code></pre><h2 id="description">DESCRIPTION</h2> <p>Run this in a package directory to bump the version and write the new data back to <code>package.json</code> and, if present, <code>npm-shrinkwrap.json</code>.</p> -<p>The <code>newversion</code> argument should be a valid semver string, <em>or</em> a -valid second argument to semver.inc (one of <code>patch</code>, <code>minor</code>, <code>major</code>, -<code>prepatch</code>, <code>preminor</code>, <code>premajor</code>, <code>prerelease</code>). In the second case, -the existing version will be incremented by 1 in the specified field.</p> +<p>The <code>newversion</code> argument should be a valid semver string, a +valid second argument to <a href="https://github.com/npm/node-semver#functions">semver.inc</a> (one of <code>patch</code>, <code>minor</code>, <code>major</code>, +<code>prepatch</code>, <code>preminor</code>, <code>premajor</code>, <code>prerelease</code>), or <code>from-git</code>. In the second case, +the existing version will be incremented by 1 in the specified field. +<code>from-git</code> will try to read the latest git tag, and use that as the new npm version.</p> <p>If run in a git repo, it will also create a version commit and tag. This behavior is controlled by <code>git-tag-version</code> (see below), and can be disabled on the command line by running <code>npm --no-git-tag-version version</code>. @@ -99,5 +100,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.3.12</p> +<p id="footer">npm-version — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-view.html b/deps/npm/html/doc/cli/npm-view.html index 965b3504e2..0e3f034be3 100644 --- a/deps/npm/html/doc/cli/npm-view.html +++ b/deps/npm/html/doc/cli/npm-view.html @@ -83,5 +83,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.3.12</p> +<p id="footer">npm-view — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm-whoami.html b/deps/npm/html/doc/cli/npm-whoami.html index 1b954c864b..dd98b1af77 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.3.12</p> +<p id="footer">npm-whoami — npm@3.6.0</p> diff --git a/deps/npm/html/doc/cli/npm.html b/deps/npm/html/doc/cli/npm.html index b43ccda47f..09836480be 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.3.12</p> +<p>3.6.0</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 @@ -109,16 +109,16 @@ easily by doing <code>npm view npm contributors</code>.</p> <p>If you would like to contribute, but don't know what to work on, check the issues list or ask on the mailing list.</p> <ul> -<li><a href="http://github.com/npm/npm/issues">http://github.com/npm/npm/issues</a></li> -<li><a href="mailto:npm-@googlegroups.com">npm-@googlegroups.com</a></li> +<li><a href="https://github.com/npm/npm/issues">https://github.com/npm/npm/issues</a></li> +<li><a href="mailto:npm-@googlegroups.com">npm-@googlegroups.com</a></li> </ul> <h2 id="bugs">BUGS</h2> <p>When you find issues, please report them:</p> <ul> <li>web: -<a href="http://github.com/npm/npm/issues">http://github.com/npm/npm/issues</a></li> +<a href="https://github.com/npm/npm/issues">https://github.com/npm/npm/issues</a></li> <li>email: -<a href="mailto:npm-@googlegroups.com">npm-@googlegroups.com</a></li> +<a href="mailto:npm-@googlegroups.com">npm-@googlegroups.com</a></li> </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> @@ -128,7 +128,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> @@ -140,7 +140,6 @@ will no doubt tell you to put the output in a gist or email.</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-index.html">npm-index(7)</a></li> -<li><a href="../api/npm.html">npm(3)</a></li> </ul> </div> @@ -154,5 +153,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.3.12</p> +<p id="footer">npm — npm@3.6.0</p> diff --git a/deps/npm/html/doc/files/npm-folders.html b/deps/npm/html/doc/files/npm-folders.html index a4e6733276..4dd7b317a2 100644 --- a/deps/npm/html/doc/files/npm-folders.html +++ b/deps/npm/html/doc/files/npm-folders.html @@ -25,11 +25,10 @@ is installed.</li> </ul> <h3 id="prefix-configuration">prefix Configuration</h3> <p>The <code>prefix</code> config defaults to the location where node is installed. -On most systems, this is <code>/usr/local</code>, and most of the time is the same -as node's <code>process.installPrefix</code>.</p> -<p>On windows, this is the exact location of the node.exe binary. On Unix -systems, it's one level up, since node is typically installed at -<code>{prefix}/bin/node</code> rather than <code>{prefix}/node.exe</code>.</p> +On most systems, this is <code>/usr/local</code>. On windows, this is the exact +location of the node.exe binary. On Unix systems, it's one level up, +since node is typically installed at <code>{prefix}/bin/node</code> rather than +<code>{prefix}/node.exe</code>.</p> <p>When the <code>global</code> flag is set, npm installs things into this prefix. When it is not set, it uses the root of the current package, or the current working directory if not in a package already.</p> @@ -44,7 +43,7 @@ Global installs on Windows go to <code>{prefix}/node_modules</code> (that is, no <p>Scoped packages are installed the same way, except they are grouped together in a sub-folder of the relevant <code>node_modules</code> folder with the name of that scope prefix by the @ symbol, e.g. <code>npm install @myorg/package</code> would place -the package in <code>{prefix}/node_modules/@myorg/package</code>. See <code><a href="../misc/scopes.html">scopes(7)</a></code> for +the package in <code>{prefix}/node_modules/@myorg/package</code>. See <code><a href="../misc/scope.html">scope(7)</a></code> for more details.</p> <p>If you wish to <code>require()</code> a package, then install it locally.</p> <h3 id="executables">Executables</h3> @@ -184,5 +183,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.3.12</p> +<p id="footer">npm-folders — npm@3.6.0</p> diff --git a/deps/npm/html/doc/files/npm-global.html b/deps/npm/html/doc/files/npm-global.html index a4e6733276..4dd7b317a2 100644 --- a/deps/npm/html/doc/files/npm-global.html +++ b/deps/npm/html/doc/files/npm-global.html @@ -25,11 +25,10 @@ is installed.</li> </ul> <h3 id="prefix-configuration">prefix Configuration</h3> <p>The <code>prefix</code> config defaults to the location where node is installed. -On most systems, this is <code>/usr/local</code>, and most of the time is the same -as node's <code>process.installPrefix</code>.</p> -<p>On windows, this is the exact location of the node.exe binary. On Unix -systems, it's one level up, since node is typically installed at -<code>{prefix}/bin/node</code> rather than <code>{prefix}/node.exe</code>.</p> +On most systems, this is <code>/usr/local</code>. On windows, this is the exact +location of the node.exe binary. On Unix systems, it's one level up, +since node is typically installed at <code>{prefix}/bin/node</code> rather than +<code>{prefix}/node.exe</code>.</p> <p>When the <code>global</code> flag is set, npm installs things into this prefix. When it is not set, it uses the root of the current package, or the current working directory if not in a package already.</p> @@ -44,7 +43,7 @@ Global installs on Windows go to <code>{prefix}/node_modules</code> (that is, no <p>Scoped packages are installed the same way, except they are grouped together in a sub-folder of the relevant <code>node_modules</code> folder with the name of that scope prefix by the @ symbol, e.g. <code>npm install @myorg/package</code> would place -the package in <code>{prefix}/node_modules/@myorg/package</code>. See <code><a href="../misc/scopes.html">scopes(7)</a></code> for +the package in <code>{prefix}/node_modules/@myorg/package</code>. See <code><a href="../misc/scope.html">scope(7)</a></code> for more details.</p> <p>If you wish to <code>require()</code> a package, then install it locally.</p> <h3 id="executables">Executables</h3> @@ -184,5 +183,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.3.12</p> +<p id="footer">npm-folders — npm@3.6.0</p> diff --git a/deps/npm/html/doc/files/npm-json.html b/deps/npm/html/doc/files/npm-json.html index 92d14ba6c5..9c2bb70c63 100644 --- a/deps/npm/html/doc/files/npm-json.html +++ b/deps/npm/html/doc/files/npm-json.html @@ -24,7 +24,7 @@ changes to the version.</p> <p>The name is what your thing is called.</p> <p>Some rules:</p> <ul> -<li>The name must be shorter than 214 characters. This includes the scope for +<li>The name must be less than or equal to 214 characters. This includes the scope for scoped packages.</li> <li>The name can't start with a dot or an underscore.</li> <li>New packages must not have uppercase letters in the name.</li> @@ -85,8 +85,8 @@ current SPDX license identifier for the license you're using, like this:</p> <pre><code>{ "license" : "BSD-3-Clause" } </code></pre><p>You can check <a href="https://spdx.org/licenses/">the full list of SPDX license IDs</a>. Ideally you should pick one that is -<a href="http://opensource.org/licenses/alphabetical">OSI</a> approved.</p> -<p>If your package is licensed under multiple common licenses, use an <a href="http://npmjs.com/package/spdx">SPDX license +<a href="https://opensource.org/licenses/alphabetical">OSI</a> approved.</p> +<p>If your package is licensed under multiple common licenses, use an <a href="https://npmjs.com/package/spdx">SPDX license expression syntax version 2.0 string</a>, like this:</p> <pre><code>{ "license" : "(ISC OR GPL-3.0)" } </code></pre><p>If you are using a license that hasn't been assigned an SPDX identifier, or if @@ -309,7 +309,7 @@ tarball or git URL.</p> <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>path/path/path</code> See Local Paths below</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> <pre><code>{ "dependencies" : @@ -545,7 +545,7 @@ ignored.</p> <li><a href="../misc/npm-faq.html">npm-faq(7)</a></li> <li><a href="../cli/npm-install.html">npm-install(1)</a></li> <li><a href="../cli/npm-publish.html">npm-publish(1)</a></li> -<li><a href="../cli/npm-rm.html">npm-rm(1)</a></li> +<li><a href="../cli/npm-uninstall.html">npm-uninstall(1)</a></li> </ul> </div> @@ -559,5 +559,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.3.12</p> +<p id="footer">package.json — npm@3.6.0</p> diff --git a/deps/npm/html/doc/files/npmrc.html b/deps/npm/html/doc/files/npmrc.html index dc50a18c81..7ce572a4e7 100644 --- a/deps/npm/html/doc/files/npmrc.html +++ b/deps/npm/html/doc/files/npmrc.html @@ -83,5 +83,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.3.12</p> +<p id="footer">npmrc — npm@3.6.0</p> diff --git a/deps/npm/html/doc/files/package.json.html b/deps/npm/html/doc/files/package.json.html index 92d14ba6c5..9c2bb70c63 100644 --- a/deps/npm/html/doc/files/package.json.html +++ b/deps/npm/html/doc/files/package.json.html @@ -24,7 +24,7 @@ changes to the version.</p> <p>The name is what your thing is called.</p> <p>Some rules:</p> <ul> -<li>The name must be shorter than 214 characters. This includes the scope for +<li>The name must be less than or equal to 214 characters. This includes the scope for scoped packages.</li> <li>The name can't start with a dot or an underscore.</li> <li>New packages must not have uppercase letters in the name.</li> @@ -85,8 +85,8 @@ current SPDX license identifier for the license you're using, like this:</p> <pre><code>{ "license" : "BSD-3-Clause" } </code></pre><p>You can check <a href="https://spdx.org/licenses/">the full list of SPDX license IDs</a>. Ideally you should pick one that is -<a href="http://opensource.org/licenses/alphabetical">OSI</a> approved.</p> -<p>If your package is licensed under multiple common licenses, use an <a href="http://npmjs.com/package/spdx">SPDX license +<a href="https://opensource.org/licenses/alphabetical">OSI</a> approved.</p> +<p>If your package is licensed under multiple common licenses, use an <a href="https://npmjs.com/package/spdx">SPDX license expression syntax version 2.0 string</a>, like this:</p> <pre><code>{ "license" : "(ISC OR GPL-3.0)" } </code></pre><p>If you are using a license that hasn't been assigned an SPDX identifier, or if @@ -309,7 +309,7 @@ tarball or git URL.</p> <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>path/path/path</code> See Local Paths below</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> <pre><code>{ "dependencies" : @@ -545,7 +545,7 @@ ignored.</p> <li><a href="../misc/npm-faq.html">npm-faq(7)</a></li> <li><a href="../cli/npm-install.html">npm-install(1)</a></li> <li><a href="../cli/npm-publish.html">npm-publish(1)</a></li> -<li><a href="../cli/npm-rm.html">npm-rm(1)</a></li> +<li><a href="../cli/npm-uninstall.html">npm-uninstall(1)</a></li> </ul> </div> @@ -559,5 +559,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.3.12</p> +<p id="footer">package.json — npm@3.6.0</p> diff --git a/deps/npm/html/doc/index.html b/deps/npm/html/doc/index.html index 36fcbe74c3..b00cd30c96 100644 --- a/deps/npm/html/doc/index.html +++ b/deps/npm/html/doc/index.html @@ -52,6 +52,8 @@ <p>Get help on npm</p> <h3 id="npm-init-1-"><a href="cli/npm-init.html">npm-init(1)</a></h3> <p>Interactively create a package.json file</p> +<h3 id="npm-install-test-1-"><a href="cli/npm-install-test.html">npm-install-test(1)</a></h3> +<p>Install package(s) and run tests</p> <h3 id="npm-install-1-"><a href="cli/npm-install.html">npm-install(1)</a></h3> <p>Install a package</p> <h3 id="npm-link-1-"><a href="cli/npm-link.html">npm-link(1)</a></h3> @@ -134,8 +136,6 @@ <p>Developer Guide</p> <h3 id="npm-disputes-7-"><a href="misc/npm-disputes.html">npm-disputes(7)</a></h3> <p>Handling Module Name Disputes</p> -<h3 id="npm-faq-7-"><a href="misc/npm-faq.html">npm-faq(7)</a></h3> -<p>Frequently Asked Questions</p> <h3 id="npm-index-7-"><a href="misc/npm-index.html">npm-index(7)</a></h3> <p>Index of all npm documentation</p> <h3 id="npm-orgs-7-"><a href="misc/npm-orgs.html">npm-orgs(7)</a></h3> @@ -162,5 +162,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.3.12</p> +<p id="footer">npm-index — npm@3.6.0</p> diff --git a/deps/npm/html/doc/misc/npm-coding-style.html b/deps/npm/html/doc/misc/npm-coding-style.html index 757272863d..b65041aca6 100644 --- a/deps/npm/html/doc/misc/npm-coding-style.html +++ b/deps/npm/html/doc/misc/npm-coding-style.html @@ -154,5 +154,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.3.12</p> +<p id="footer">npm-coding-style — npm@3.6.0</p> diff --git a/deps/npm/html/doc/misc/npm-config.html b/deps/npm/html/doc/misc/npm-config.html index 74b3c7bfc6..20e92a3981 100644 --- a/deps/npm/html/doc/misc/npm-config.html +++ b/deps/npm/html/doc/misc/npm-config.html @@ -203,7 +203,7 @@ explicitly used, and that only GET requests use the cache.</p> <p>A client certificate to pass when accessing the registry.</p> <h3 id="color">color</h3> <ul> -<li>Default: true on Posix, false on Windows</li> +<li>Default: true</li> <li>Type: Boolean or <code>"always"</code></li> </ul> <p>If false, never shows colors. If <code>"always"</code> then always shows colors. @@ -332,6 +332,17 @@ current working directory.</li> <li>Type: path</li> </ul> <p>The config file to read for global config options.</p> +<h3 id="global-style">global-style</h3> +<ul> +<li>Default: false</li> +<li>Type: Boolean</li> +</ul> +<p>Causes npm to install the package into your local <code>node_modules</code> folder with +the same layout it uses with the global <code>node_modules</code> folder. Only your +direct dependencies will show in <code>node_modules</code> and everything they depend +on will be flattened in their <code>node_modules</code> folders. This obviously will +elminate some deduping. If used with <code>legacy-bundling</code>, <code>legacy-bundling</code> will be +preferred.</p> <h3 id="group">group</h3> <ul> <li>Default: GID of the current process</li> @@ -424,6 +435,15 @@ change. Only the output from <code>npm ls --json</code> is currently valid.</p> <li>Type: String</li> </ul> <p>A client key to pass when accessing the registry.</p> +<h3 id="legacy-bundling">legacy-bundling</h3> +<ul> +<li>Default: false</li> +<li>Type: Boolean</li> +</ul> +<p>Causes npm to install the package such that versions of npm prior to 1.4, +such as the one included with node 0.8, can install the package. This +eliminates all automatic deduping. If used with <code>global-style</code> this option +will be preferred.</p> <h3 id="link">link</h3> <ul> <li>Default: false</li> @@ -739,7 +759,7 @@ particular, use care when overriding this setting for public packages.</p> on success, but left behind on failure for forensic purposes.</p> <h3 id="unicode">unicode</h3> <ul> -<li>Default: true on windows and mac/unix systems with a unicode locale</li> +<li>Default: false on windows, true on mac/unix systems with a unicode locale</li> <li>Type: Boolean</li> </ul> <p>When set to true, npm uses unicode characters in the tree output. When @@ -829,5 +849,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.3.12</p> +<p id="footer">npm-config — npm@3.6.0</p> diff --git a/deps/npm/html/doc/misc/npm-developers.html b/deps/npm/html/doc/misc/npm-developers.html index 3da7d91621..d509c6edbc 100644 --- a/deps/npm/html/doc/misc/npm-developers.html +++ b/deps/npm/html/doc/misc/npm-developers.html @@ -96,7 +96,7 @@ include something that is excluded by your <code>.gitignore</code> file, you can create an empty <code>.npmignore</code> file to override it. Like <code>git</code>, <code>npm</code> looks for <code>.npmignore</code> and <code>.gitignore</code> files in all subdirectories of your package, not only the root directory.</p> -<p><code>.npmignore</code> files follow the <a href="http://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#Ignoring-Files">same pattern rules</a> +<p><code>.npmignore</code> files follow the <a href="https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#Ignoring-Files">same pattern rules</a> as <code>.gitignore</code> files:</p> <ul> <li>Blank lines or lines starting with <code>#</code> are ignored.</li> @@ -161,7 +161,7 @@ bring in your module's main module.</p> </code></pre><p>and then follow the prompts.</p> <p>This is documented better in <a href="../cli/npm-adduser.html">npm-adduser(1)</a>.</p> <h2 id="publish-your-package">Publish your package</h2> -<p>This part's easy. IN the root of your folder, do this:</p> +<p>This part's easy. In the root of your folder, do this:</p> <pre><code>npm publish </code></pre><p>You can give publish a url to a tarball, or a filename of a tarball, or a path to a folder.</p> @@ -195,5 +195,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.3.12</p> +<p id="footer">npm-developers — npm@3.6.0</p> diff --git a/deps/npm/html/doc/misc/npm-disputes.html b/deps/npm/html/doc/misc/npm-disputes.html index 0962b39b5a..948cdbc973 100644 --- a/deps/npm/html/doc/misc/npm-disputes.html +++ b/deps/npm/html/doc/misc/npm-disputes.html @@ -13,7 +13,7 @@ <h2 id="synopsis">SYNOPSIS</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> @@ -51,12 +51,12 @@ Joe's appropriate course of action in each case is the same.</p> 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 +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 +<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> </ol> @@ -112,5 +112,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.3.12</p> +<p id="footer">npm-disputes — npm@3.6.0</p> diff --git a/deps/npm/html/doc/misc/npm-faq.html b/deps/npm/html/doc/misc/npm-faq.html deleted file mode 100644 index fa0cc22eff..0000000000 --- a/deps/npm/html/doc/misc/npm-faq.html +++ /dev/null @@ -1,312 +0,0 @@ -<!doctype html> -<html> - <title>npm-faq</title> - <meta http-equiv="content-type" value="text/html;utf-8"> - <link rel="stylesheet" type="text/css" href="../../static/style.css"> - <link rel="canonical" href="https://www.npmjs.org/doc/misc/npm-faq.html"> - <script async=true src="../../static/toc.js"></script> - - <body> - <div id="wrapper"> - -<h1><a href="../misc/npm-faq.html">npm-faq</a></h1> <p>Frequently Asked Questions</p> -<h2 id="where-can-i-find-these-docs-in-html-">Where can I find these docs in HTML?</h2> -<p><a href="https://docs.npmjs.com/">https://docs.npmjs.com/</a>, or run:</p> -<pre><code>npm config set viewer browser -</code></pre><p>This command will set the npm docs to open in your default web browser rather than <code>man</code>.</p> -<h2 id="it-didn-t-work-">It didn't work.</h2> -<p>Please provide a little more detail, search for the error via <a href="https://google.com">Google</a> or <a href="http://stackoverflow.com/search?q=npm">StackOverflow npm</a> to see if another developer has encountered a similar problem.</p> -<h2 id="why-didn-t-it-work-">Why didn't it work?</h2> -<p>I don't know yet.</p> -<p>Try reading the error output first, ensure this is a true npm issue and not a package issue. If you are having an issue with a package dependency, please submit your error to that particular package maintainer.</p> -<p>For any npm issues, try following the instructions, or even retracing your steps. If the issue continues to persist, submit a bug with the steps to reproduce, please include the operating system you are working on, along with the error you recieve.</p> -<h2 id="where-does-npm-put-stuff-">Where does npm put stuff?</h2> -<p>See <code><a href="../files/npm-folders.html">npm-folders(5)</a></code></p> -<p>tl;dr:</p> -<ul> -<li>Use the <code>npm root</code> command to see where modules go, and the <code>npm bin</code> -command to see where executables go</li> -<li>Global installs are different from local installs. If you install -something with the <code>-g</code> flag, then its executables go in <code>npm bin -g</code> -and its modules go in <code>npm root -g</code>.</li> -</ul> -<h2 id="how-do-i-install-something-on-my-computer-in-a-central-location-">How do I install something on my computer in a central location?</h2> -<p>Install it globally by tacking <code>-g</code> or <code>--global</code> to the command. (This -is especially important for command line utilities that need to add -their bins to the global system <code>PATH</code>.)</p> -<h2 id="i-installed-something-globally-but-i-can-t-require-it">I installed something globally, but I can't <code>require()</code> it</h2> -<p>Install it locally.</p> -<p>The global install location is a place for command-line utilities -to put their bins in the system <code>PATH</code>. It's not for use with <code>require()</code>.</p> -<p>If you <code>require()</code> a module in your code, then that means it's a -dependency, and a part of your program. You need to install it locally -in your program.</p> -<h2 id="why-can-t-npm-just-put-everything-in-one-place-like-other-package-managers-">Why can't npm just put everything in one place, like other package managers?</h2> -<p>Not every change is an improvement, but every improvement is a change. -This would be like asking git to do network IO for every commit. It's -not going to happen, because it's a terrible idea that causes more -problems than it solves.</p> -<p>It is much harder to avoid dependency conflicts without nesting -dependencies. This is fundamental to the way that npm works, and has -proven to be an extremely successful approach. See <code><a href="../files/npm-folders.html">npm-folders(5)</a></code> for -more details.</p> -<p>If you want a package to be installed in one place, and have all your -programs reference the same copy of it, then use the <code>npm link</code> command. -That's what it's for. Install it globally, then link it into each -program that uses it.</p> -<h2 id="whatever-i-really-want-the-old-style-everything-global-style-">Whatever, I really want the old style 'everything global' style.</h2> -<p>Write your own package manager. You could probably even wrap up <code>npm</code> -in a shell script if you really wanted to.</p> -<p>npm will not help you do something that is known to be a bad idea.</p> -<h2 id="should-i-check-my-node_modules-folder-into-git-">Should I check my <code>node_modules</code> folder into git?</h2> -<p>Usually, no. Allow npm to resolve dependencies for your packages.</p> -<p>For packages you <strong>deploy</strong>, such as websites and apps, -you should use npm shrinkwrap to lock down your full dependency tree:</p> -<p><a href="https://docs.npmjs.com/cli/shrinkwrap">https://docs.npmjs.com/cli/shrinkwrap</a></p> -<p>If you are paranoid about depending on the npm ecosystem, -you should run a private npm mirror or a private cache.</p> -<p>If you want 100% confidence in being able to reproduce the specific bytes -included in a deployment, you should use an additional mechanism that can -verify contents rather than versions. For example, -Amazon machine images, DigitalOcean snapshots, Heroku slugs, or simple tarballs.</p> -<h2 id="is-it-npm-or-npm-or-npm-">Is it 'npm' or 'NPM' or 'Npm'?</h2> -<p>npm should never be capitalized unless it is being displayed in a -location that is customarily all-caps (such as the title of man pages.)</p> -<h2 id="if-npm-is-an-acronym-why-is-it-never-capitalized-">If 'npm' is an acronym, why is it never capitalized?</h2> -<p>Contrary to the belief of many, "npm" is not in fact an abbreviation for -"Node Package Manager". It is a recursive bacronymic abbreviation for -"npm is not an acronym". (If it was "ninaa", then it would be an -acronym, and thus incorrectly named.)</p> -<p>"NPM", however, <em>is</em> an acronym (more precisely, a capitonym) for the -National Association of Pastoral Musicians. You can learn more -about them at <a href="http://npm.org/">http://npm.org/</a>.</p> -<p>In software, "NPM" is a Non-Parametric Mapping utility written by -Chris Rorden. You can analyze pictures of brains with it. Learn more -about the (capitalized) NPM program at <a href="http://www.cabiatl.com/mricro/npm/">http://www.cabiatl.com/mricro/npm/</a>.</p> -<p>The first seed that eventually grew into this flower was a bash utility -named "pm", which was a shortened descendent of "pkgmakeinst", a -bash function that was used to install various different things on different -platforms, most often using Yahoo's <code>yinst</code>. If <code>npm</code> was ever an -acronym for anything, it was <code>node pm</code> or maybe <code>new pm</code>.</p> -<p>So, in all seriousness, the "npm" project is named after its command-line -utility, which was organically selected to be easily typed by a right-handed -programmer using a US QWERTY keyboard layout, ending with the -right-ring-finger in a postition to type the <code>-</code> key for flags and -other command-line arguments. That command-line utility is always -lower-case, though it starts most sentences it is a part of.</p> -<h2 id="how-do-i-list-installed-packages-">How do I list installed packages?</h2> -<p><code>npm ls</code></p> -<h2 id="how-do-i-search-for-packages-">How do I search for packages?</h2> -<p><code>npm search</code></p> -<p>Arguments are greps. <code>npm search jsdom</code> shows jsdom packages.</p> -<h2 id="how-do-i-update-npm-">How do I update npm?</h2> -<pre><code>npm install npm -g -</code></pre><p>You can also update all outdated local packages by doing <code>npm update</code> without -any arguments, or global packages by doing <code>npm update -g</code>.</p> -<p>Occasionally, the version of npm will progress such that the current -version cannot be properly installed with the version that you have -installed already. (Consider, if there is ever a bug in the <code>update</code> -command.)</p> -<p>In those cases, you can do this:</p> -<pre><code>curl https://www.npmjs.com/install.sh | sh -</code></pre><h2 id="what-is-a-package-">What is a <code>package</code>?</h2> -<p>A package is:</p> -<ul> -<li>a) a folder containing a program described by a package.json file</li> -<li>b) a gzipped tarball containing (a)</li> -<li>c) a url that resolves to (b)</li> -<li>d) a <code><name>@<version></code> that is published on the registry with (c)</li> -<li>e) a <code><name>@<tag></code> that points to (d)</li> -<li>f) a <code><name></code> that has a "latest" tag satisfying (e)</li> -<li>g) a <code>git</code> url that, when cloned, results in (a).</li> -</ul> -<p>Even if you never publish your package, you can still get a lot of -benefits of using npm if you just want to write a node program (a), and -perhaps if you also want to be able to easily install it elsewhere -after packing it up into a tarball (b).</p> -<p>Git urls can be of the form:</p> -<pre><code>git://github.com/user/project.git#commit-ish -git+ssh://user@hostname:project.git#commit-ish -git+http://user@hostname/project/blah.git#commit-ish -git+https://user@hostname/project/blah.git#commit-ish -</code></pre><p>The <code>commit-ish</code> can be any tag, sha, or branch which can be supplied as -an argument to <code>git checkout</code>. The default is <code>master</code>.</p> -<h2 id="what-is-a-module-">What is a <code>module</code>?</h2> -<p>A module is anything that can be loaded with <code>require()</code> in a Node.js -program. The following things are all examples of things that can be -loaded as modules:</p> -<ul> -<li>A folder with a <code>package.json</code> file containing a <code>main</code> field.</li> -<li>A folder with an <code>index.js</code> file in it.</li> -<li>A JavaScript file.</li> -</ul> -<p>Most npm packages are modules, because they are libraries that you -load with <code>require</code>. However, there's no requirement that an npm -package be a module! Some only contain an executable command-line -interface, and don't provide a <code>main</code> field for use in Node programs.</p> -<p>Almost all npm packages (at least, those that are Node programs) -<em>contain</em> many modules within them (because every file they load with -<code>require()</code> is a module).</p> -<p>In the context of a Node program, the <code>module</code> is also the thing that -was loaded <em>from</em> a file. For example, in the following program:</p> -<pre><code>var req = require('request') -</code></pre><p>we might say that "The variable <code>req</code> refers to the <code>request</code> module".</p> -<h2 id="so-why-is-it-the-node_modules-folder-but-package-json-file-why-not-node_packages-or-module-json-">So, why is it the "<code>node_modules</code>" folder, but "<code>package.json</code>" file? Why not <code>node_packages</code> or <code>module.json</code>?</h2> -<p>The <code>package.json</code> file defines the package. (See "What is a -package?" above.)</p> -<p>The <code>node_modules</code> folder is the place Node.js looks for modules. -(See "What is a module?" above.)</p> -<p>For example, if you create a file at <code>node_modules/foo.js</code> and then -had a program that did <code>var f = require('foo.js')</code> then it would load -the module. However, <code>foo.js</code> is not a "package" in this case, -because it does not have a package.json.</p> -<p>Alternatively, if you create a package which does not have an -<code>index.js</code> or a <code>"main"</code> field in the <code>package.json</code> file, then it is -not a module. Even if it's installed in <code>node_modules</code>, it can't be -an argument to <code>require()</code>.</p> -<h2 id="-node_modules-is-the-name-of-my-deity-s-arch-rival-and-a-forbidden-word-in-my-religion-can-i-configure-npm-to-use-a-different-folder-"><code>"node_modules"</code> is the name of my deity's arch-rival, and a Forbidden Word in my religion. Can I configure npm to use a different folder?</h2> -<p>No. This will never happen. This question comes up sometimes, -because it seems silly from the outside that npm couldn't just be -configured to put stuff somewhere else, and then npm could load them -from there. It's an arbitrary spelling choice, right? What's the big -deal?</p> -<p>At the time of this writing, the string <code>'node_modules'</code> appears 151 -times in 53 separate files in npm and node core (excluding tests and -documentation).</p> -<p>Some of these references are in node's built-in module loader. Since -npm is not involved <strong>at all</strong> at run-time, node itself would have to -be configured to know where you've decided to stick stuff. Complexity -hurdle #1. Since the Node module system is locked, this cannot be -changed, and is enough to kill this request. But I'll continue, in -deference to your deity's delicate feelings regarding spelling.</p> -<p>Many of the others are in dependencies that npm uses, which are not -necessarily tightly coupled to npm (in the sense that they do not read -npm's configuration files, etc.) Each of these would have to be -configured to take the name of the <code>node_modules</code> folder as a -parameter. Complexity hurdle #2.</p> -<p>Furthermore, npm has the ability to "bundle" dependencies by adding -the dep names to the <code>"bundledDependencies"</code> list in package.json, -which causes the folder to be included in the package tarball. What -if the author of a module bundles its dependencies, and they use a -different spelling for <code>node_modules</code>? npm would have to rename the -folder at publish time, and then be smart enough to unpack it using -your locally configured name. Complexity hurdle #3.</p> -<p>Furthermore, what happens when you <em>change</em> this name? Fine, it's -easy enough the first time, just rename the <code>node_modules</code> folders to -<code>./blergyblerp/</code> or whatever name you choose. But what about when you -change it again? npm doesn't currently track any state about past -configuration settings, so this would be rather difficult to do -properly. It would have to track every previous value for this -config, and always accept any of them, or else yesterday's install may -be broken tomorrow. Complexity hurdle #4.</p> -<p>Never going to happen. The folder is named <code>node_modules</code>. It is -written indelibly in the Node Way, handed down from the ancient times -of Node 0.3.</p> -<h2 id="how-do-i-install-node-with-npm-">How do I install node with npm?</h2> -<p>You don't. Try one of these node version managers:</p> -<p>Unix:</p> -<ul> -<li><a href="http://github.com/isaacs/nave">http://github.com/isaacs/nave</a></li> -<li><a href="http://github.com/visionmedia/n">http://github.com/visionmedia/n</a></li> -<li><a href="http://github.com/creationix/nvm">http://github.com/creationix/nvm</a></li> -</ul> -<p>Windows:</p> -<ul> -<li><a href="http://github.com/marcelklehr/nodist">http://github.com/marcelklehr/nodist</a></li> -<li><a href="https://github.com/coreybutler/nvm-windows">https://github.com/coreybutler/nvm-windows</a></li> -<li><a href="https://github.com/hakobera/nvmw">https://github.com/hakobera/nvmw</a></li> -<li><a href="https://github.com/nanjingboy/nvmw">https://github.com/nanjingboy/nvmw</a></li> -</ul> -<h2 id="how-can-i-use-npm-for-development-">How can I use npm for development?</h2> -<p>See <code><a href="../misc/npm-developers.html">npm-developers(7)</a></code> and <code><a href="../files/package.json.html">package.json(5)</a></code>.</p> -<p>You'll most likely want to <code>npm link</code> your development folder. That's -awesomely handy.</p> -<p>To set up your own private registry, check out <code><a href="../misc/npm-registry.html">npm-registry(7)</a></code>.</p> -<h2 id="can-i-list-a-url-as-a-dependency-">Can I list a url as a dependency?</h2> -<p>Yes. It should be a url to a gzipped tarball containing a single folder -that has a package.json in its root, or a git url. -(See "what is a package?" above.)</p> -<h2 id="how-do-i-symlink-to-a-dev-folder-so-i-don-t-have-to-keep-re-installing-">How do I symlink to a dev folder so I don't have to keep re-installing?</h2> -<p>See <code><a href="../cli/npm-link.html">npm-link(1)</a></code></p> -<h2 id="the-package-registry-website-what-is-that-exactly-">The package registry website. What is that exactly?</h2> -<p>See <code><a href="../misc/npm-registry.html">npm-registry(7)</a></code>.</p> -<h2 id="i-forgot-my-password-and-can-t-publish-how-do-i-reset-it-">I forgot my password, and can't publish. How do I reset it?</h2> -<p>Go to <a href="https://npmjs.com/forgot">https://npmjs.com/forgot</a>.</p> -<h2 id="i-get-econnrefused-a-lot-what-s-up-">I get ECONNREFUSED a lot. What's up?</h2> -<p>Either the registry is down, or node's DNS isn't able to reach out.</p> -<p>To check if the registry is down, open up -<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a> in a web browser. This will also tell -you if you are just unable to access the internet for some reason.</p> -<p>If the registry IS down, let us know by emailing <a href="mailto:support@npmjs.com">support@npmjs.com</a> -or posting an issue at <a href="https://github.com/npm/npm/issues">https://github.com/npm/npm/issues</a>. If it's -down for the world (and not just on your local network) then we're -probably already being pinged about it.</p> -<p>You can also often get a faster response by visiting the #npm channel -on Freenode IRC.</p> -<h2 id="why-no-namespaces-">Why no namespaces?</h2> -<p>npm has only one global namespace. If you want to namespace your own packages, -you may: simply use the <code>-</code> character to separate the names or use scoped -packages. npm is a mostly anarchic system. There is not sufficient need to -impose namespace rules on everyone.</p> -<p>As of 2.0, npm supports scoped packages, which allow you to publish a group of -related modules without worrying about name collisions.</p> -<p>Every npm user owns the scope associated with their username. For example, the -user named <code>npm</code> owns the scope <code>@npm</code>. Scoped packages are published inside a -scope by naming them as if they were files under the scope directory, e.g., by -setting <code>name</code> in <code>package.json</code> to <code>@npm/npm</code>.</p> -<p>Scoped packages are supported by the public npm registry. The npm client is -backwards-compatible with un-scoped registries, so it can be used to work with -scoped and un-scoped registries at the same time.</p> -<p>Unscoped packages can only depend on other unscoped packages. Scoped packages -can depend on packages from their own scope, a different scope, or the public -registry (unscoped).</p> -<p>For the current documentation of scoped packages, see -<a href="https://docs.npmjs.com/misc/scope">https://docs.npmjs.com/misc/scope</a></p> -<p>References:</p> -<ol> -<li><p>For the reasoning behind the "one global namespace", please see this -discussion: <a href="https://github.com/npm/npm/issues/798">https://github.com/npm/npm/issues/798</a> (TL;DR: It doesn't -actually make things better, and can make them worse.)</p> -</li> -<li><p>For the pre-implementation discussion of the scoped package feature, see -this discussion: <a href="https://github.com/npm/npm/issues/5239">https://github.com/npm/npm/issues/5239</a></p> -</li> -</ol> -<h2 id="who-does-npm-">Who does npm?</h2> -<p>npm was originally written by Isaac Z. Schlueter, and many others have -contributed to it, some of them quite substantially.</p> -<p>The npm open source project, The npm Registry, and <a href="https://www.npmjs.com">the community -website</a> are maintained and operated by the -good folks at <a href="http://www.npmjs.com">npm, Inc.</a></p> -<h2 id="i-have-a-question-or-request-not-addressed-here-where-should-i-put-it-">I have a question or request not addressed here. Where should I put it?</h2> -<p>Post an issue on the github project:</p> -<ul> -<li><a href="https://github.com/npm/npm/issues">https://github.com/npm/npm/issues</a></li> -</ul> -<h2 id="why-does-npm-hate-me-">Why does npm hate me?</h2> -<p>npm is not capable of hatred. It loves everyone, especially you.</p> -<h2 id="see-also">SEE ALSO</h2> -<ul> -<li><a href="../cli/npm.html">npm(1)</a></li> -<li><a href="../misc/npm-developers.html">npm-developers(7)</a></li> -<li><a href="../files/package.json.html">package.json(5)</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="../files/npmrc.html">npmrc(5)</a></li> -<li><a href="../misc/npm-config.html">npm-config(7)</a></li> -<li><a href="../files/npm-folders.html">npm-folders(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-faq — npm@3.3.12</p> - diff --git a/deps/npm/html/doc/misc/npm-index.html b/deps/npm/html/doc/misc/npm-index.html index ae0950efd7..2342f319d6 100644 --- a/deps/npm/html/doc/misc/npm-index.html +++ b/deps/npm/html/doc/misc/npm-index.html @@ -52,6 +52,8 @@ <p>Get help on npm</p> <h3 id="npm-init-1-"><a href="../cli/npm-init.html">npm-init(1)</a></h3> <p>Interactively create a package.json file</p> +<h3 id="npm-install-test-1-"><a href="../cli/npm-install-test.html">npm-install-test(1)</a></h3> +<p>Install package(s) and run tests</p> <h3 id="npm-install-1-"><a href="../cli/npm-install.html">npm-install(1)</a></h3> <p>Install a package</p> <h3 id="npm-link-1-"><a href="../cli/npm-link.html">npm-link(1)</a></h3> @@ -134,8 +136,6 @@ <p>Developer Guide</p> <h3 id="npm-disputes-7-"><a href="../misc/npm-disputes.html">npm-disputes(7)</a></h3> <p>Handling Module Name Disputes</p> -<h3 id="npm-faq-7-"><a href="../misc/npm-faq.html">npm-faq(7)</a></h3> -<p>Frequently Asked Questions</p> <h3 id="npm-index-7-"><a href="../misc/npm-index.html">npm-index(7)</a></h3> <p>Index of all npm documentation</p> <h3 id="npm-orgs-7-"><a href="../misc/npm-orgs.html">npm-orgs(7)</a></h3> @@ -162,4 +162,4 @@ <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.3.12</p> +<p id="footer">npm-index — npm@3.6.0</p> diff --git a/deps/npm/html/doc/misc/npm-orgs.html b/deps/npm/html/doc/misc/npm-orgs.html index a42a4863f8..07a766ed89 100644 --- a/deps/npm/html/doc/misc/npm-orgs.html +++ b/deps/npm/html/doc/misc/npm-orgs.html @@ -86,4 +86,4 @@ <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.3.12</p> +<p id="footer">npm-orgs — npm@3.6.0</p> diff --git a/deps/npm/html/doc/misc/npm-registry.html b/deps/npm/html/doc/misc/npm-registry.html index 9068310aef..881a2bbae0 100644 --- a/deps/npm/html/doc/misc/npm-registry.html +++ b/deps/npm/html/doc/misc/npm-registry.html @@ -17,10 +17,10 @@ package info.</p> <p>Additionally, npm's package registry implementation supports several write APIs as well, to allow for publishing packages and managing user account information.</p> -<p>The official public npm registry is at <a href="http://registry.npmjs.org/">http://registry.npmjs.org/</a>. It +<p>The official public npm registry is at <a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>. It is powered by a CouchDB database, of which there is a public mirror at -<a href="http://skimdb.npmjs.com/registry">http://skimdb.npmjs.com/registry</a>. The code for the couchapp is -available at <a href="http://github.com/npm/npm-registry-couchapp">http://github.com/npm/npm-registry-couchapp</a>.</p> +<a href="https://skimdb.npmjs.com/registry">https://skimdb.npmjs.com/registry</a>. The code for the couchapp is +available at <a href="https://github.com/npm/npm-registry-couchapp">https://github.com/npm/npm-registry-couchapp</a>.</p> <p>The registry URL used is determined by the scope of the package (see <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>, @@ -70,5 +70,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.3.12</p> +<p id="footer">npm-registry — npm@3.6.0</p> diff --git a/deps/npm/html/doc/misc/npm-scope.html b/deps/npm/html/doc/misc/npm-scope.html index 2aac1b177d..dd2895914d 100644 --- a/deps/npm/html/doc/misc/npm-scope.html +++ b/deps/npm/html/doc/misc/npm-scope.html @@ -91,5 +91,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.3.12</p> +<p id="footer">npm-scope — npm@3.6.0</p> diff --git a/deps/npm/html/doc/misc/npm-scripts.html b/deps/npm/html/doc/misc/npm-scripts.html index ed50c1caf8..50a5c2f578 100644 --- a/deps/npm/html/doc/misc/npm-scripts.html +++ b/deps/npm/html/doc/misc/npm-scripts.html @@ -134,10 +134,10 @@ see this in the script:</p> , "uninstall" : "scripts/uninstall.js" } } -</code></pre><p>then the <code>scripts/install.js</code> will be called for the install, -post-install, stages of the lifecycle, and the <code>scripts/uninstall.js</code> -would be called when the package is uninstalled. Since -<code>scripts/install.js</code> is running for three different phases, it would +</code></pre><p>then <code>scripts/install.js</code> will be called for the install +and post-install stages of the lifecycle, and <code>scripts/uninstall.js</code> +will be called when the package is uninstalled. Since +<code>scripts/install.js</code> is running for two different phases, it would be wise in this case to look at the <code>npm_lifecycle_event</code> environment variable.</p> <p>If you want to run a make command, you can do so. This works just @@ -176,7 +176,7 @@ print a warning and exit successfully.</li> by simply describing your package appropriately. In general, this will lead to a more robust and consistent state.</li> <li>Inspect the env to determine where to put things. For instance, if -the <code>npm_config_binroot</code> environ is set to <code>/home/user/bin</code>, then +the <code>npm_config_binroot</code> environment variable is set to <code>/home/user/bin</code>, then don't try to install executables into <code>/usr/local/bin</code>. The user probably set it up that way for a reason.</li> <li>Don't prefix your script commands with "sudo". If root permissions @@ -207,5 +207,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.3.12</p> +<p id="footer">npm-scripts — npm@3.6.0</p> diff --git a/deps/npm/html/doc/misc/removing-npm.html b/deps/npm/html/doc/misc/removing-npm.html index 90e345a4a2..96dc31259c 100644 --- a/deps/npm/html/doc/misc/removing-npm.html +++ b/deps/npm/html/doc/misc/removing-npm.html @@ -42,7 +42,7 @@ modules. To track those down, you can do the following:</p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../../doc/README.html">README</a></li> -<li><a href="../cli/npm-rm.html">npm-rm(1)</a></li> +<li><a href="../cli/npm-uninstall.html">npm-uninstall(1)</a></li> <li><a href="../cli/npm-prune.html">npm-prune(1)</a></li> </ul> @@ -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.3.12</p> +<p id="footer">removing-npm — npm@3.6.0</p> diff --git a/deps/npm/html/doc/misc/semver.html b/deps/npm/html/doc/misc/semver.html index c73b0534f6..616b09333f 100644 --- a/deps/npm/html/doc/misc/semver.html +++ b/deps/npm/html/doc/misc/semver.html @@ -94,7 +94,7 @@ similar risk on the <em>next</em> set of prerelease versions.</p> <h4 id="prerelease-identifiers">Prerelease Identifiers</h4> <p>The method <code>.inc</code> takes an additional <code>identifier</code> string argument that will append the value of the string as a prerelease identifier:</p> -<pre><code class="lang-javascript">> semver.inc('1.2.3', 'pre', 'beta') +<pre><code class="lang-javascript">> semver.inc('1.2.3', 'prerelease', 'beta') '1.2.4-beta.0' </code></pre> <p>command-line example:</p> @@ -199,6 +199,26 @@ zero.</p> <li><code>^1.x</code> := <code>>=1.0.0 <2.0.0</code></li> <li><code>^0.x</code> := <code>>=0.0.0 <1.0.0</code></li> </ul> +<h3 id="range-grammar">Range Grammar</h3> +<p>Putting all this together, here is a Backus-Naur grammar for ranges, +for the benefit of parser authors:</p> +<pre><code class="lang-bnf">range-set ::= range ( logical-or range ) * +logical-or ::= ( ' ' ) * '||' ( ' ' ) * +range ::= hyphen | simple ( ' ' simple ) * | '' +hyphen ::= partial ' - ' partial +simple ::= primitive | partial | tilde | caret +primitive ::= ( '<' | '>' | '>=' | '<=' | '=' | ) partial +partial ::= xr ( '.' xr ( '.' xr qualifier ? )? )? +xr ::= 'x' | 'X' | '*' | nr +nr ::= '0' | ['1'-'9']['0'-'9']+ +tilde ::= '~' partial +caret ::= '^' partial +qualifier ::= ( '-' pre )? ( '+' build )? +pre ::= parts +build ::= parts +parts ::= part ( '.' part ) * +part ::= nr | [-0-9A-Za-z]+ +</code></pre> <h2 id="functions">Functions</h2> <p>All methods and classes take a final <code>loose</code> boolean argument that, if true, will be more forgiving about not-quite-valid semver strings. @@ -282,5 +302,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.3.12</p> +<p id="footer">semver — npm@3.6.0</p> |