diff options
author | Rebecca Turner <me@re-becca.org> | 2015-10-09 23:13:57 -0700 |
---|---|---|
committer | Jeremiah Senkpiel <fishrock123@rocketmail.com> | 2015-10-22 13:56:09 -0400 |
commit | 41923c0c0795cfa6c465821387fca88fe8811367 (patch) | |
tree | 853587bc888fde98f714d72050edceb4785145de /deps/npm/html/doc/cli | |
parent | 9b8886446dd183cee26adf9c603f8e1cd5da74bd (diff) | |
download | node-new-41923c0c0795cfa6c465821387fca88fe8811367.tar.gz |
deps: upgrade npm to 3.3.6
PR-URL: https://github.com/nodejs/node/pull/3310
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Diffstat (limited to 'deps/npm/html/doc/cli')
51 files changed, 207 insertions, 218 deletions
diff --git a/deps/npm/html/doc/cli/npm-access.html b/deps/npm/html/doc/cli/npm-access.html index 761aea5e52..15eb34c86a 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@2.14.7</p> +<p id="footer">npm-access — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-adduser.html b/deps/npm/html/doc/cli/npm-adduser.html index a331bfbbf5..5b19a67f4f 100644 --- a/deps/npm/html/doc/cli/npm-adduser.html +++ b/deps/npm/html/doc/cli/npm-adduser.html @@ -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@2.14.7</p> +<p id="footer">npm-adduser — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-bin.html b/deps/npm/html/doc/cli/npm-bin.html index 12c598c62f..050f864259 100644 --- a/deps/npm/html/doc/cli/npm-bin.html +++ b/deps/npm/html/doc/cli/npm-bin.html @@ -11,7 +11,7 @@ <h1><a href="../cli/npm-bin.html">npm-bin</a></h1> <p>Display npm bin folder</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm bin +<pre><code>npm bin [--global] </code></pre><h2 id="description">DESCRIPTION</h2> <p>Print the folder where npm will install executables.</p> <h2 id="see-also">SEE ALSO</h2> @@ -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@2.14.7</p> +<p id="footer">npm-bin — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-bugs.html b/deps/npm/html/doc/cli/npm-bugs.html index fcd2b88da1..02a2e932c1 100644 --- a/deps/npm/html/doc/cli/npm-bugs.html +++ b/deps/npm/html/doc/cli/npm-bugs.html @@ -11,8 +11,7 @@ <h1><a href="../cli/npm-bugs.html">npm-bugs</a></h1> <p>Bugs for a package in a web browser maybe</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm bugs <pkgname> -npm bugs (with no args in a package dir) +<pre><code>npm bugs [<pkgname>] </code></pre><h2 id="description">DESCRIPTION</h2> <p>This command tries to guess at the likely location of a package's bug tracker URL, and then tries to open it using the <code>--browser</code> @@ -54,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@2.14.7</p> +<p id="footer">npm-bugs — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-build.html b/deps/npm/html/doc/cli/npm-build.html index 9bc9161432..b8689f190e 100644 --- a/deps/npm/html/doc/cli/npm-build.html +++ b/deps/npm/html/doc/cli/npm-build.html @@ -11,7 +11,7 @@ <h1><a href="../cli/npm-build.html">npm-build</a></h1> <p>Build a package</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm build <package-folder> +<pre><code>npm build [<package-folder>] </code></pre><ul> <li><code><package-folder></code>: A folder containing a <code>package.json</code> file in its root.</li> @@ -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@2.14.7</p> +<p id="footer">npm-build — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-bundle.html b/deps/npm/html/doc/cli/npm-bundle.html index 81a65c1692..18cb054696 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@2.14.7</p> +<p id="footer">npm-bundle — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-cache.html b/deps/npm/html/doc/cli/npm-cache.html index 8517937475..e9da236630 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@2.14.7</p> +<p id="footer">npm-cache — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-completion.html b/deps/npm/html/doc/cli/npm-completion.html index 15f71fb290..48f05ec3f6 100644 --- a/deps/npm/html/doc/cli/npm-completion.html +++ b/deps/npm/html/doc/cli/npm-completion.html @@ -11,14 +11,16 @@ <h1><a href="../cli/npm-completion.html">npm-completion</a></h1> <p>Tab Completion for npm</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>. <(npm completion) +<pre><code>source <(npm completion) </code></pre><h2 id="description">DESCRIPTION</h2> <p>Enables tab-completion in all npm commands.</p> <p>The synopsis above loads the completions into your current shell. Adding it to your ~/.bashrc or ~/.zshrc will make the completions available -everywhere.</p> -<p>You may of course also pipe the output of npm completion to a file +everywhere:</p> +<pre><code>npm completion >> ~/.bashrc +npm completion >> ~/.zshrc +</code></pre><p>You may of course also pipe the output of npm completion to a file such as <code>/usr/local/etc/bash_completion.d/npm</code> if you have a system that will read that file for you.</p> <p>When <code>COMP_CWORD</code>, <code>COMP_LINE</code>, and <code>COMP_POINT</code> are defined in the @@ -42,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@2.14.7</p> +<p id="footer">npm-completion — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-config.html b/deps/npm/html/doc/cli/npm-config.html index d73762fe02..86b13ad581 100644 --- a/deps/npm/html/doc/cli/npm-config.html +++ b/deps/npm/html/doc/cli/npm-config.html @@ -16,7 +16,6 @@ npm config get <key> npm config delete <key> npm config list npm config edit -npm c [set|get|delete|list] npm get <key> npm set <key> <value> [--global] </code></pre><h2 id="description">DESCRIPTION</h2> @@ -66,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@2.14.7</p> +<p id="footer">npm-config — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-dedupe.html b/deps/npm/html/doc/cli/npm-dedupe.html index b8bab0074d..520d5158d7 100644 --- a/deps/npm/html/doc/cli/npm-dedupe.html +++ b/deps/npm/html/doc/cli/npm-dedupe.html @@ -31,20 +31,16 @@ be more effectively shared by multiple dependent packages.</p> </code></pre><p>Because of the hierarchical nature of node's module lookup, b and d will both get their dependency met by the single c package at the root level of the tree.</p> +<p>The deduplication algorithm walks the tree, moving each dependency as far +up in the tree as possible, even if duplicates are not found. This will +result in both a flat and deduplicated tree.</p> <p>If a suitable version exists at the target location in the tree already, then it will be left untouched, but the other duplicates will be deleted.</p> -<p>If no suitable version can be found, then a warning is printed, and -nothing is done.</p> -<p>If any arguments are supplied, then they are filters, and only the -named packages will be touched.</p> -<p>Note that this operation transforms the dependency tree, and may -result in packages getting updated versions, perhaps from the npm -registry.</p> -<p>This feature is experimental, and may change in future versions.</p> -<p>The <code>--tag</code> argument will apply to all of the affected dependencies. If a -tag with the given name exists, the tagged version is preferred over newer -versions.</p> +<p>Arguments are ignored. Dedupe always acts on the entire tree.</p> +<p>Modules</p> +<p>Note that this operation transforms the dependency tree, but will never +result in new modules being installed.</p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../cli/npm-ls.html">npm-ls(1)</a></li> @@ -63,5 +59,5 @@ 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-dedupe — npm@2.14.7</p> +<p id="footer">npm-dedupe — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-deprecate.html b/deps/npm/html/doc/cli/npm-deprecate.html index 9549631b69..33d09e1959 100644 --- a/deps/npm/html/doc/cli/npm-deprecate.html +++ b/deps/npm/html/doc/cli/npm-deprecate.html @@ -11,7 +11,7 @@ <h1><a href="../cli/npm-deprecate.html">npm-deprecate</a></h1> <p>Deprecate a version of a package</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm deprecate <name>[@<version>] <message> +<pre><code>npm deprecate <pkg>[@<version>] <message> </code></pre><h2 id="description">DESCRIPTION</h2> <p>This command will update the npm registry entry for a package, providing a deprecation warning to all who attempt to install it.</p> @@ -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@2.14.7</p> +<p id="footer">npm-deprecate — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-dist-tag.html b/deps/npm/html/doc/cli/npm-dist-tag.html index 2a683e7106..3435ecc32b 100644 --- a/deps/npm/html/doc/cli/npm-dist-tag.html +++ b/deps/npm/html/doc/cli/npm-dist-tag.html @@ -77,5 +77,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@2.14.7</p> +<p id="footer">npm-dist-tag — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-docs.html b/deps/npm/html/doc/cli/npm-docs.html index 0e17c157fc..7a9028f783 100644 --- a/deps/npm/html/doc/cli/npm-docs.html +++ b/deps/npm/html/doc/cli/npm-docs.html @@ -12,9 +12,9 @@ <h1><a href="../cli/npm-docs.html">npm-docs</a></h1> <p>Docs for a package in a web browser maybe</p> <h2 id="synopsis">SYNOPSIS</h2> <pre><code>npm docs [<pkgname> [<pkgname> ...]] -npm docs (with no args in a package dir) +npm docs . npm home [<pkgname> [<pkgname> ...]] -npm home (with no args in a package dir) +npm home . </code></pre><h2 id="description">DESCRIPTION</h2> <p>This command tries to guess at the likely location of a package's documentation URL, and then tries to open it using the <code>--browser</code> @@ -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@2.14.7</p> +<p id="footer">npm-docs — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-edit.html b/deps/npm/html/doc/cli/npm-edit.html index 79c150019e..8d1bfc1efa 100644 --- a/deps/npm/html/doc/cli/npm-edit.html +++ b/deps/npm/html/doc/cli/npm-edit.html @@ -11,7 +11,7 @@ <h1><a href="../cli/npm-edit.html">npm-edit</a></h1> <p>Edit an installed package</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm edit <name>[@<version>] +<pre><code>npm edit <pkg>[@<version>] </code></pre><h2 id="description">DESCRIPTION</h2> <p>Opens the package folder in the default editor (or whatever you've configured as the npm <code>editor</code> config -- see <code><a href="../misc/npm-config.html">npm-config(7)</a></code>.)</p> @@ -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@2.14.7</p> +<p id="footer">npm-edit — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-explore.html b/deps/npm/html/doc/cli/npm-explore.html index 29364ad4f3..8be4b5af9a 100644 --- a/deps/npm/html/doc/cli/npm-explore.html +++ b/deps/npm/html/doc/cli/npm-explore.html @@ -11,7 +11,7 @@ <h1><a href="../cli/npm-explore.html">npm-explore</a></h1> <p>Browse an installed package</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm explore <name> [ -- <cmd>] +<pre><code>npm explore <pkg> [ -- <cmd>] </code></pre><h2 id="description">DESCRIPTION</h2> <p>Spawn a subshell in the directory of the installed package specified.</p> <p>If a command is specified, then it is run in the subshell, which then @@ -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@2.14.7</p> +<p id="footer">npm-explore — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-help-search.html b/deps/npm/html/doc/cli/npm-help-search.html index 2ff4a11ac6..ad9182bfdf 100644 --- a/deps/npm/html/doc/cli/npm-help-search.html +++ b/deps/npm/html/doc/cli/npm-help-search.html @@ -11,7 +11,7 @@ <h1><a href="../cli/npm-help-search.html">npm-help-search</a></h1> <p>Search npm help documentation</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm help-search some search terms +<pre><code>npm help-search <text> </code></pre><h2 id="description">DESCRIPTION</h2> <p>This command will search the npm markdown documentation files for the terms provided, and then list the results, sorted by relevance.</p> @@ -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@2.14.7</p> +<p id="footer">npm-help-search — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-help.html b/deps/npm/html/doc/cli/npm-help.html index 13b670b596..6678a564a3 100644 --- a/deps/npm/html/doc/cli/npm-help.html +++ b/deps/npm/html/doc/cli/npm-help.html @@ -11,8 +11,7 @@ <h1><a href="../cli/npm-help.html">npm-help</a></h1> <p>Get help on npm</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm help <topic> -npm help some search terms +<pre><code>npm help <term> [<terms..>] </code></pre><h2 id="description">DESCRIPTION</h2> <p>If supplied a topic, then show the appropriate documentation page.</p> <p>If the topic does not exist, or if multiple terms are provided, then run @@ -52,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@2.14.7</p> +<p id="footer">npm-help — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-init.html b/deps/npm/html/doc/cli/npm-init.html index d9c3d05247..c3e3443039 100644 --- a/deps/npm/html/doc/cli/npm-init.html +++ b/deps/npm/html/doc/cli/npm-init.html @@ -11,7 +11,7 @@ <h1><a href="../cli/npm-init.html">npm-init</a></h1> <p>Interactively create a package.json file</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm init [-f|--force|-y|--yes] +<pre><code>npm init [--force|-f|--yes|-y] </code></pre><h2 id="description">DESCRIPTION</h2> <p>This will ask you a bunch of questions, and then write a package.json for you.</p> <p>It attempts to make reasonable guesses about what you want things to be set to, @@ -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@2.14.7</p> +<p id="footer">npm-init — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-install.html b/deps/npm/html/doc/cli/npm-install.html index ab3e03f9ba..63057da690 100644 --- a/deps/npm/html/doc/cli/npm-install.html +++ b/deps/npm/html/doc/cli/npm-install.html @@ -11,15 +11,17 @@ <h1><a href="../cli/npm-install.html">npm-install</a></h1> <p>Install a package</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm install (with no args in a package dir) +<pre><code>npm install (with no args, in package dir) +npm install [<@scope>/]<name> +npm install [<@scope>/]<name>@<tag> +npm install [<@scope>/]<name>@<version> +npm install [<@scope>/]<name>@<version range> npm install <tarball file> npm install <tarball url> npm install <folder> -npm install [@<scope>/]<name> [--save|--save-dev|--save-optional] [--save-exact] -npm install [@<scope>/]<name>@<tag> -npm install [@<scope>/]<name>@<version> -npm install [@<scope>/]<name>@<version range> -npm i (with any of the previous argument usage) + +alias: npm i +common options: [--save|--save-dev|--save-optional] [--save-exact] [--dry-run] </code></pre><h2 id="description">DESCRIPTION</h2> <p>This command installs a package, and any packages that it depends on. If the package has a shrinkwrap file, the installation of dependencies will be driven @@ -32,7 +34,7 @@ by that. See <a href="../cli/npm-shrinkwrap.html">npm-shrinkwrap(1)</a>.</p> <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>f) a <code><name></code> that has a "latest" tag satisfying (e)</li> -<li>g) a <code><git remote url></code> that resolves to (b)</li> +<li>g) a <code><git remote url></code> that resolves to (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 @@ -65,7 +67,7 @@ after packing it up into a tarball (b).</p> <p> Example:</p> <pre><code> npm install https://github.com/indexzero/forever/tarball/v0.5.6 </code></pre></li> -<li><p><code>npm install [@<scope>/]<name> [--save|--save-dev|--save-optional]</code>:</p> +<li><p><code>npm install [<@scope>/]<name> [--save|--save-dev|--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> <p> In most cases, this will install the latest version @@ -86,6 +88,8 @@ package.json, there is an additional, optional flag:</p> <li><p><code>--save-exact</code>: Saved dependencies will be configured with an exact version rather than using npm's default semver range operator.</p> +<p>Further, if you have an <code>npm-shrinkwrap.json</code> then it will be updated as +well.</p> <p><code><scope></code> is optional. The package will be downloaded from the registry associated with the specified scope. If no registry is associated with the given scope the default registry is assumed. See <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code>.</p> @@ -107,7 +111,7 @@ npm install readable-stream --save --save-exact working directory, then it will try to install that, and only try to fetch the package by name if it is not valid. </code></pre><ul> -<li><p><code>npm install [@<scope>/]<name>@<tag></code>:</p> +<li><p><code>npm install [<@scope>/]<name>@<tag></code>:</p> <p> Install the version of the package that is referenced by the specified tag. If the tag does not exist in the registry data for that package, then this will fail.</p> @@ -115,14 +119,14 @@ fetch the package by name if it is not valid. <pre><code> npm install sax@latest npm install @myorg/mypackage@latest </code></pre></li> -<li><p><code>npm install [@<scope>/]<name>@<version></code>:</p> +<li><p><code>npm install [<@scope>/]<name>@<version></code>:</p> <p> Install the specified version of the package. This will fail if the version has not been published to the registry.</p> <p> Example:</p> <pre><code> npm install sax@0.1.1 npm install @myorg/privatepackage@1.5.0 </code></pre></li> -<li><p><code>npm install [@<scope>/]<name>@<version range></code>:</p> +<li><p><code>npm install [<@scope>/]<name>@<version range></code>:</p> <p> Install a version of the package matching the specified version range. This will follow the same rules for resolving dependencies described in <code><a href="../files/package.json.html">package.json(5)</a></code>.</p> <p> Note that most version ranges must be put in quotes so that your shell will @@ -132,9 +136,9 @@ fetch the package by name if it is not valid. npm install @myorg/privatepackage@">=0.1.0 <0.2.0" </code></pre></li> <li><p><code>npm install <git remote url></code>:</p> -<p> Install a package by cloning a git remote url. The format of the git - url is:</p> -<pre><code> <protocol>://[<user>[:<password>]@]<hostname>[:<port>][:/]<path>[#<commit-ish>] +<p> Installs the package from the hosted git provider, cloning it with + <code>git</code>. First it tries via the https (git with github) and if that fails, via ssh.</p> +<pre><code> <protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>[#<commit-ish>] </code></pre><p> <code><protocol></code> is one of <code>git</code>, <code>git+ssh</code>, <code>git+http</code>, or <code>git+https</code>. If no <code><commit-ish></code> is specified, then <code>master</code> is used.</p> @@ -195,6 +199,8 @@ For example:</p> </code></pre><p>The <code>--tag</code> argument will apply to all of the specified install targets. If a tag with the given name exists, the tagged version is preferred over newer versions.</p> +<p>The <code>--dry-run</code> argument will report in the usual way what the install would +have done without actually installing anything.</p> <p>The <code>--force</code> argument will force npm to fetch remote resources even if a local copy exists on disk.</p> <pre><code>npm install sax --force @@ -210,27 +216,39 @@ being installed.</p> shrinkwrap file and use the package.json instead.</p> <p>The <code>--nodedir=/path/to/node/source</code> argument will allow npm to find the node source code so that npm can compile native modules.</p> +<p>The <code>--only={prod[uction]|dev[elopment]}</code> argument will cause either only +<code>devDependencies</code> or only non-<code>devDependencies</code> to be installed.</p> <p>See <code><a href="../misc/npm-config.html">npm-config(7)</a></code>. Many of the configuration params have some effect on installation, since that's most of what npm does.</p> <h2 id="algorithm">ALGORITHM</h2> <p>To install a package, npm uses the following algorithm:</p> -<pre><code>install(where, what, family, ancestors) -fetch what, unpack to <where>/node_modules/<what> -for each dep in what.dependencies - resolve dep to precise version -for each dep@version in what.dependencies - not in <where>/node_modules/<what>/node_modules/* - and not in <family> - add precise version deps to <family> - install(<where>/node_modules/<what>, dep, family) +<pre><code>load the existing node_modules tree from disk +clone the tree +fetch the package.json and assorted metadata and add it to the clone +walk the clone and add any missing dependencies + dependencies will be added as close to the top as is possible + without breaking any other modules +compare the original tree with the cloned tree and make a list of +actions to take to convert one to the other +execute all of the actions, deepest first + kinds of actions are install, update, remove and move </code></pre><p>For this <code>package{dep}</code> structure: <code>A{B,C}, B{C}, C{D}</code>, this algorithm produces:</p> <pre><code>A +-- B -`-- C - `-- D ++-- C ++-- D </code></pre><p>That is, the dependency from B to C is satisfied by the fact that A -already caused C to be installed at a higher level.</p> +already caused C to be installed at a higher level. D is still installed +at the top level because nothing conflicts with it.</p> +<p>For <code>A{B,C}, B{C,D@1}, C{D@2}</code>, this algorithm produces:</p> +<pre><code>A ++-- B ++-- C + `-- D@2 ++-- D@1 +</code></pre><p>Because B's D@1 will be installed in the top leve, C now has to install D@2 +privately for itself.</p> <p>See <a href="../files/npm-folders.html">npm-folders(5)</a> for a more detailed description of the specific folder structures that npm creates.</p> <h3 id="limitations-of-npm-s-install-algorithm">Limitations of npm's Install Algorithm</h3> @@ -277,5 +295,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@2.14.7</p> +<p id="footer">npm-install — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-link.html b/deps/npm/html/doc/cli/npm-link.html index 322d02d469..0a944aff94 100644 --- a/deps/npm/html/doc/cli/npm-link.html +++ b/deps/npm/html/doc/cli/npm-link.html @@ -11,9 +11,10 @@ <h1><a href="../cli/npm-link.html">npm-link</a></h1> <p>Symlink a package folder</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm link (in package folder) -npm link [@<scope>/]<pkgname> -npm ln (with any of the previous argument usage) +<pre><code>npm link (in package dir) +npm link [<@scope>/]<pkg>[@<version>] + +alias: npm ln </code></pre><h2 id="description">DESCRIPTION</h2> <p>Package linking is a two-step process.</p> <p>First, <code>npm link</code> in a package folder will create a globally-installed @@ -72,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@2.14.7</p> +<p id="footer">npm-link — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-logout.html b/deps/npm/html/doc/cli/npm-logout.html index 16b97daae3..7fa51c9c13 100644 --- a/deps/npm/html/doc/cli/npm-logout.html +++ b/deps/npm/html/doc/cli/npm-logout.html @@ -11,7 +11,7 @@ <h1><a href="../cli/npm-logout.html">npm-logout</a></h1> <p>Log out of the registry</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm logout [--registry=url] [--scope=@orgname] +<pre><code>npm logout [--registry=<url>] [--scope=<@scope>] </code></pre><h2 id="description">DESCRIPTION</h2> <p>When logged into a registry that supports token-based authentication, tell the server to end this token's session. This will invalidate the token everywhere @@ -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@2.14.7</p> +<p id="footer">npm-logout — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-ls.html b/deps/npm/html/doc/cli/npm-ls.html index f36d7952cf..73144c1681 100644 --- a/deps/npm/html/doc/cli/npm-ls.html +++ b/deps/npm/html/doc/cli/npm-ls.html @@ -11,10 +11,9 @@ <h1><a href="../cli/npm-ls.html">npm-ls</a></h1> <p>List installed packages</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm list [[@<scope>/]<pkg> ...] -npm ls [[@<scope>/]<pkg> ...] -npm la [[@<scope>/]<pkg> ...] -npm ll [[@<scope>/]<pkg> ...] +<pre><code>npm ls [[<@scope>/]<pkg> ...] + +aliases: list, la, ll </code></pre><h2 id="description">DESCRIPTION</h2> <p>This command will print to stdout all the versions of packages that are installed, as well as their dependencies, in a tree-structure.</p> @@ -22,13 +21,15 @@ 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@2.14.7 /path/to/npm +<pre><code>npm@3.3.6 /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> <p>If a project specifies git urls for dependencies these are shown in parentheses after the name@version to make it easier for users to recognize potential forks of a project.</p> +<p>The tree shown is the logical dependency tree, based on package +dependencies, not the physical layout of your node_modules folder.</p> <p>When run as <code>ll</code> or <code>la</code>, it shows extended information by default.</p> <h2 id="configuration">CONFIGURATION</h2> <h3 id="json">json</h3> @@ -73,6 +74,12 @@ project.</p> <li>Default: false</li> </ul> <p>Display only the dependency tree for packages in <code>devDependencies</code>.</p> +<h3 id="only">only</h3> +<ul> +<li>Type: String</li> +</ul> +<p>When "dev" or "development", is an alias to <code>dev</code>.</p> +<p>When "prod" or "production", is an alias to <code>production</code>.`</p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../cli/npm-config.html">npm-config(1)</a></li> @@ -97,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@2.14.7</p> +<p id="footer">npm-ls — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-outdated.html b/deps/npm/html/doc/cli/npm-outdated.html index 29728e96ae..5a5f67b942 100644 --- a/deps/npm/html/doc/cli/npm-outdated.html +++ b/deps/npm/html/doc/cli/npm-outdated.html @@ -11,7 +11,7 @@ <h1><a href="../cli/npm-outdated.html">npm-outdated</a></h1> <p>Check for outdated packages</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm outdated [<name> [<name> ...]] +<pre><code>npm outdated [[<@scope>/]<pkg> ...] </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> @@ -67,5 +67,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@2.14.7</p> +<p id="footer">npm-outdated — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-owner.html b/deps/npm/html/doc/cli/npm-owner.html index 603043dc6e..6cbc0f4bde 100644 --- a/deps/npm/html/doc/cli/npm-owner.html +++ b/deps/npm/html/doc/cli/npm-owner.html @@ -11,9 +11,9 @@ <h1><a href="../cli/npm-owner.html">npm-owner</a></h1> <p>Manage package owners</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm owner ls <package name> -npm owner add <user> <package name> -npm owner rm <user> <package name> +<pre><code>npm owner add <user> [<@scope>/]<pkg> +npm owner rm <user> [<@scope>/]<pkg> +npm owner ls [<@scope>/]<pkg> </code></pre><h2 id="description">DESCRIPTION</h2> <p>Manage ownership of published packages.</p> <ul> @@ -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@2.14.7</p> +<p id="footer">npm-owner — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-pack.html b/deps/npm/html/doc/cli/npm-pack.html index 77bf5578bb..7abf2f572b 100644 --- a/deps/npm/html/doc/cli/npm-pack.html +++ b/deps/npm/html/doc/cli/npm-pack.html @@ -11,13 +11,13 @@ <h1><a href="../cli/npm-pack.html">npm-pack</a></h1> <p>Create a tarball from a package</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm pack [<pkg> [<pkg> ...]] +<pre><code>npm pack [[<@scope>/]<pkg>...] </code></pre><h2 id="description">DESCRIPTION</h2> <p>For anything that's installable (that is, a package folder, tarball, -tarball url, name@tag, name@version, or name), this command will fetch -it to the cache, and then copy the tarball to the current working -directory as <code><name>-<version>.tgz</code>, and then write the filenames out to -stdout.</p> +tarball url, name@tag, name@version, name, or scoped name), this +command will fetch it to the cache, and then copy the tarball to the +current working directory as <code><name>-<version>.tgz</code>, and then write +the filenames out to stdout.</p> <p>If the same package is specified multiple times, then the file will be overwritten the second time.</p> <p>If no arguments are supplied, then npm packs the current package folder.</p> @@ -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@2.14.7</p> +<p id="footer">npm-pack — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-ping.html b/deps/npm/html/doc/cli/npm-ping.html index e10095ec5a..4a78052b6c 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@2.14.7</p> +<p id="footer">npm-ping — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-prefix.html b/deps/npm/html/doc/cli/npm-prefix.html index 96d63d7507..26aa01fda0 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@2.14.7</p> +<p id="footer">npm-prefix — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-prune.html b/deps/npm/html/doc/cli/npm-prune.html index d90b0fb25a..88d57ece8c 100644 --- a/deps/npm/html/doc/cli/npm-prune.html +++ b/deps/npm/html/doc/cli/npm-prune.html @@ -11,8 +11,7 @@ <h1><a href="../cli/npm-prune.html">npm-prune</a></h1> <p>Remove extraneous packages</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm prune [<name> [<name ...]] -npm prune [<name> [<name ...]] [--production] +<pre><code>npm prune [[<@scope>/]<pkg>...] [--production] </code></pre><h2 id="description">DESCRIPTION</h2> <p>This command removes "extraneous" packages. If a package name is provided, then only packages matching one of the supplied names are @@ -41,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@2.14.7</p> +<p id="footer">npm-prune — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-publish.html b/deps/npm/html/doc/cli/npm-publish.html index b6372b2644..bc5884d872 100644 --- a/deps/npm/html/doc/cli/npm-publish.html +++ b/deps/npm/html/doc/cli/npm-publish.html @@ -11,8 +11,10 @@ <h1><a href="../cli/npm-publish.html">npm-publish</a></h1> <p>Publish a package</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm publish <tarball> [--tag <tag>] [--access <public|restricted>] -npm publish <folder> [--tag <tag>] [--access <public|restricted>] +<pre><code>npm publish [<tarball>|<folder>] [--tag <tag>] [--access <public|restricted>] + +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 @@ -66,5 +68,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@2.14.7</p> +<p id="footer">npm-publish — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-rebuild.html b/deps/npm/html/doc/cli/npm-rebuild.html index 4fb2d48108..92ef96425b 100644 --- a/deps/npm/html/doc/cli/npm-rebuild.html +++ b/deps/npm/html/doc/cli/npm-rebuild.html @@ -11,13 +11,10 @@ <h1><a href="../cli/npm-rebuild.html">npm-rebuild</a></h1> <p>Rebuild a package</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm rebuild [<name> [<name> ...]] -npm rb [<name> [<name> ...]] -</code></pre><ul> -<li><code><name></code>: -The package to rebuild</li> -</ul> -<h2 id="description">DESCRIPTION</h2> +<pre><code>npm rebuild [[<@scope>/<name>]...] + +alias: npm rb +</code></pre><h2 id="description">DESCRIPTION</h2> <p>This command runs the <code>npm build</code> command on the matched folders. This is useful when you install a new version of node, and must recompile all your C++ addons with the new binary.</p> @@ -38,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@2.14.7</p> +<p id="footer">npm-rebuild — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-repo.html b/deps/npm/html/doc/cli/npm-repo.html index d66da6ab92..1d1445eafb 100644 --- a/deps/npm/html/doc/cli/npm-repo.html +++ b/deps/npm/html/doc/cli/npm-repo.html @@ -11,8 +11,7 @@ <h1><a href="../cli/npm-repo.html">npm-repo</a></h1> <p>Open package repository page in the browser</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm repo <pkgname> -npm repo (with no args in a package dir) +<pre><code>npm repo [<pkg>] </code></pre><h2 id="description">DESCRIPTION</h2> <p>This command tries to guess at the likely location of a package's repository URL, and then tries to open it using the <code>--browser</code> @@ -42,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@2.14.7</p> +<p id="footer">npm-repo — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-restart.html b/deps/npm/html/doc/cli/npm-restart.html index 7d9fe7b964..555c9fbeed 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@2.14.7</p> +<p id="footer">npm-restart — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-rm.html b/deps/npm/html/doc/cli/npm-rm.html deleted file mode 100644 index 1714fe27df..0000000000 --- a/deps/npm/html/doc/cli/npm-rm.html +++ /dev/null @@ -1,43 +0,0 @@ -<!doctype html> -<html> - <title>npm-rm</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-rm.html"> - <script async=true src="../../static/toc.js"></script> - - <body> - <div id="wrapper"> - -<h1><a href="../cli/npm-rm.html">npm-rm</a></h1> <p>Remove a package</p> -<h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm rm <name> -npm r <name> -npm uninstall <name> -npm un <name> -</code></pre><h2 id="description">DESCRIPTION</h2> -<p>This uninstalls a package, completely removing everything npm installed -on its behalf.</p> -<h2 id="see-also">SEE ALSO</h2> -<ul> -<li><a href="../cli/npm-prune.html">npm-prune(1)</a></li> -<li><a href="../cli/npm-install.html">npm-install(1)</a></li> -<li><a href="../files/npm-folders.html">npm-folders(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> -</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-rm — npm@2.14.7</p> - diff --git a/deps/npm/html/doc/cli/npm-root.html b/deps/npm/html/doc/cli/npm-root.html index e29dacdbea..e8e2a1890f 100644 --- a/deps/npm/html/doc/cli/npm-root.html +++ b/deps/npm/html/doc/cli/npm-root.html @@ -11,7 +11,7 @@ <h1><a href="../cli/npm-root.html">npm-root</a></h1> <p>Display npm root</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm root +<pre><code>npm root [-g] </code></pre><h2 id="description">DESCRIPTION</h2> <p>Print the effective <code>node_modules</code> folder to standard out.</p> <h2 id="see-also">SEE ALSO</h2> @@ -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@2.14.7</p> +<p id="footer">npm-root — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-run-script.html b/deps/npm/html/doc/cli/npm-run-script.html index 47f437d625..39f4d0d60b 100644 --- a/deps/npm/html/doc/cli/npm-run-script.html +++ b/deps/npm/html/doc/cli/npm-run-script.html @@ -11,8 +11,9 @@ <h1><a href="../cli/npm-run-script.html">npm-run-script</a></h1> <p>Run arbitrary package scripts</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm run-script [command] [-- <args>] -npm run [command] [-- <args>] +<pre><code>npm run-script <command> [-- <args>...] + +alias: npm run </code></pre><h2 id="description">DESCRIPTION</h2> <p>This runs an arbitrary command from a package's <code>"scripts"</code> object. If no <code>"command"</code> is provided, it will list the available scripts. <code>run[-script]</code> is @@ -57,5 +58,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@2.14.7</p> +<p id="footer">npm-run-script — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-search.html b/deps/npm/html/doc/cli/npm-search.html index 049a5faa18..25ff96e1e8 100644 --- a/deps/npm/html/doc/cli/npm-search.html +++ b/deps/npm/html/doc/cli/npm-search.html @@ -12,8 +12,8 @@ <h1><a href="../cli/npm-search.html">npm-search</a></h1> <p>Search for packages</p> <h2 id="synopsis">SYNOPSIS</h2> <pre><code>npm search [--long] [search terms ...] -npm s [search terms ...] -npm se [search terms ...] + +aliases: s, se </code></pre><h2 id="description">DESCRIPTION</h2> <p>Search the registry for packages matching the search terms.</p> <p>If a term starts with <code>/</code>, then it's interpreted as a regular expression. @@ -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@2.14.7</p> +<p id="footer">npm-search — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-shrinkwrap.html b/deps/npm/html/doc/cli/npm-shrinkwrap.html index 3d11d8e0e4..66e3b08486 100644 --- a/deps/npm/html/doc/cli/npm-shrinkwrap.html +++ b/deps/npm/html/doc/cli/npm-shrinkwrap.html @@ -72,27 +72,33 @@ when B hasn't changed at all.</p> </code></pre><p>This generates <code>npm-shrinkwrap.json</code>, which will look something like this:</p> <pre><code>{ "name": "A", - "version": "0.1.0", + "version": "1.1.0", "dependencies": { "B": { - "version": "0.0.1", + "version": "1.0.1", + "from": "B@^1.0.0", + "resolved": "https://registry.npmjs.org/B/-/B-1.0.1.tgz", "dependencies": { "C": { - "version": "0.0.1" + "version": "1.0.1", + "from": "org/C#v1.0.1", + "resolved": "git://github.com/org/C.git#5c380ae319fc4efe9e7f2d9c78b0faa588fd99b4" } } } } } -</code></pre><p>The shrinkwrap command has locked down the dependencies based on -what's currently installed in node_modules. When <code>npm install</code> -installs a package with an <code>npm-shrinkwrap.json</code> in the package -root, the shrinkwrap file (rather than <code>package.json</code> files) completely -drives the installation of that package and all of its dependencies -(recursively). So now the author publishes A@0.1.0, and subsequent -installs of this package will use B@0.0.1 and C@0.0.1, regardless the -dependencies and versions listed in A's, B's, and C's <code>package.json</code> -files.</p> +</code></pre><p>The shrinkwrap command has locked down the dependencies based on what's +currently installed in <code>node_modules</code>. The installation behavior is changed to:</p> +<ol> +<li><p>The module tree described by the shrinkwrap is reproduced. This means +reproducing the structure described in the file, using the specific files +referenced in "resolved" if available, falling back to normal package +resolution using "version" if one isn't.</p> +</li> +<li><p>The tree is walked and any missing dependencies are installed in the usual fasion.</p> +</li> +</ol> <h3 id="using-shrinkwrapped-packages">Using shrinkwrapped packages</h3> <p>Using a shrinkwrapped package is no different than using any other package: you can <code>npm install</code> it by hand, or add a dependency to your @@ -110,15 +116,14 @@ your package.</li> <ol> <li>Run <code>npm install</code> in the package root to install the current versions of all dependencies.</li> -<li>Add or update dependencies. <code>npm install</code> each new or updated -package individually and then update <code>package.json</code>. Note that they -must be explicitly named in order to be installed: running <code>npm -install</code> with no arguments will merely reproduce the existing +<li>Add or update dependencies. <code>npm install --save</code> each new or updated +package individually to update the <code>package.json</code> and the shrinkwrap. +Note that they must be explicitly named in order to be installed: running +<code>npm install</code> with no arguments will merely reproduce the existing shrinkwrap.</li> <li>Validate that the package works as expected with the new dependencies.</li> -<li>Run <code>npm shrinkwrap</code>, commit the new <code>npm-shrinkwrap.json</code>, and -publish your package.</li> +<li>Commit the new <code>npm-shrinkwrap.json</code>, and publish your package.</li> </ol> <p>You can use <a href="../cli/npm-outdated.html">npm-outdated(1)</a> to view dependencies with newer versions available.</p> @@ -164,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@2.14.7</p> +<p id="footer">npm-shrinkwrap — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-star.html b/deps/npm/html/doc/cli/npm-star.html index 6a33768b77..c6a97f4192 100644 --- a/deps/npm/html/doc/cli/npm-star.html +++ b/deps/npm/html/doc/cli/npm-star.html @@ -11,8 +11,8 @@ <h1><a href="../cli/npm-star.html">npm-star</a></h1> <p>Mark your favorite packages</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm star <pkgname> [<pkg>, ...] -npm unstar <pkgname> [<pkg>, ...] +<pre><code>npm star [<pkg>...] +npm unstar [<pkg>...] </code></pre><h2 id="description">DESCRIPTION</h2> <p>"Starring" a package means that you have some interest in it. It's a vaguely positive way to show that you care.</p> @@ -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@2.14.7</p> +<p id="footer">npm-star — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-stars.html b/deps/npm/html/doc/cli/npm-stars.html index 89b23b0a88..47aac754d3 100644 --- a/deps/npm/html/doc/cli/npm-stars.html +++ b/deps/npm/html/doc/cli/npm-stars.html @@ -11,8 +11,7 @@ <h1><a href="../cli/npm-stars.html">npm-stars</a></h1> <p>View packages marked as favorites</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm stars -npm stars [username] +<pre><code>npm stars [<user>] </code></pre><h2 id="description">DESCRIPTION</h2> <p>If you have starred a lot of neat things and want to find them again quickly this command lets you do just that.</p> @@ -37,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@2.14.7</p> +<p id="footer">npm-stars — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-start.html b/deps/npm/html/doc/cli/npm-start.html index 718160b63e..1b5fb427f1 100644 --- a/deps/npm/html/doc/cli/npm-start.html +++ b/deps/npm/html/doc/cli/npm-start.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-start — npm@2.14.7</p> +<p id="footer">npm-start — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-stop.html b/deps/npm/html/doc/cli/npm-stop.html index 2047d8e854..b7b63c2462 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@2.14.7</p> +<p id="footer">npm-stop — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-tag.html b/deps/npm/html/doc/cli/npm-tag.html index af7b2f746f..2a23eccd4a 100644 --- a/deps/npm/html/doc/cli/npm-tag.html +++ b/deps/npm/html/doc/cli/npm-tag.html @@ -11,7 +11,8 @@ <h1><a href="../cli/npm-tag.html">npm-tag</a></h1> <p>Tag a published version</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm tag <name>@<version> [<tag>] +<pre><code>[DEPRECATED] npm tag <name>@<version> [<tag>] +See `dist-tag` </code></pre><h2 id="description">DESCRIPTION</h2> <p>THIS COMMAND IS DEPRECATED. See <a href="../cli/npm-dist-tag.html">npm-dist-tag(1)</a> for details.</p> <p>Tags the specified version of the package with the specified tag, or the @@ -62,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@2.14.7</p> +<p id="footer">npm-tag — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-team.html b/deps/npm/html/doc/cli/npm-team.html index cc23b76d82..60333b6c37 100644 --- a/deps/npm/html/doc/cli/npm-team.html +++ b/deps/npm/html/doc/cli/npm-team.html @@ -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@2.14.7</p> +<p id="footer">npm-team — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-test.html b/deps/npm/html/doc/cli/npm-test.html index bcd729a748..c48b3f6070 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@2.14.7</p> +<p id="footer">npm-test — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-uninstall.html b/deps/npm/html/doc/cli/npm-uninstall.html index 8763c40adb..6d7429bbd7 100644 --- a/deps/npm/html/doc/cli/npm-uninstall.html +++ b/deps/npm/html/doc/cli/npm-uninstall.html @@ -11,8 +11,9 @@ <h1><a href="../cli/npm-rm.html">npm-rm</a></h1> <p>Remove a package</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm uninstall [@<scope>/]<package> [--save|--save-dev|--save-optional] -npm rm (with any of the previous argument usage) +<pre><code>npm uninstall [<@scope>/]<pkg>[@<version>]... [--save|--save-dev|--save-optional] + +aliases: remove, rm, r, un, unlink </code></pre><h2 id="description">DESCRIPTION</h2> <p>This uninstalls a package, completely removing everything npm installed on its behalf.</p> @@ -30,6 +31,8 @@ the package version in your main package.json:</p> <li><p><code>--save-optional</code>: Package will be removed from your <code>optionalDependencies</code>.</p> </li> </ul> +<p>Further, if you have an <code>npm-shrinkwrap.json</code> then it will be updated as +well.</p> <p>Scope is optional and follows the usual rules for <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code>.</p> <p>Examples:</p> <pre><code>npm uninstall sax --save @@ -57,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@2.14.7</p> +<p id="footer">npm-uninstall — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-unpublish.html b/deps/npm/html/doc/cli/npm-unpublish.html index 667802cd4c..a5495578f4 100644 --- a/deps/npm/html/doc/cli/npm-unpublish.html +++ b/deps/npm/html/doc/cli/npm-unpublish.html @@ -11,7 +11,7 @@ <h1><a href="../cli/npm-unpublish.html">npm-unpublish</a></h1> <p>Remove a package from the registry</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm unpublish [@<scope>/]<name>[@<version>] +<pre><code>npm unpublish [<@scope>/]<pkg>[@<version>] </code></pre><h2 id="warning">WARNING</h2> <p><strong>It is generally considered bad behavior to remove versions of a library that others are depending on!</strong></p> @@ -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@2.14.7</p> +<p id="footer">npm-unpublish — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-update.html b/deps/npm/html/doc/cli/npm-update.html index e08a2c1150..0dcbb63f30 100644 --- a/deps/npm/html/doc/cli/npm-update.html +++ b/deps/npm/html/doc/cli/npm-update.html @@ -11,7 +11,7 @@ <h1><a href="../cli/npm-update.html">npm-update</a></h1> <p>Update a package</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm update [-g] [<name> [<name> ...]] +<pre><code>npm update [-g] [<pkg>...] </code></pre><h2 id="description">DESCRIPTION</h2> <p>This command will update all the packages listed to the latest version (specified by the <code>tag</code> config), respecting semver.</p> @@ -119,5 +119,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@2.14.7</p> +<p id="footer">npm-update — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-version.html b/deps/npm/html/doc/cli/npm-version.html index 34bb9c956b..3c03604995 100644 --- a/deps/npm/html/doc/cli/npm-version.html +++ b/deps/npm/html/doc/cli/npm-version.html @@ -12,6 +12,10 @@ <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] + +'npm -v' or 'npm --version' to print npm version +'npm view <pkg> version' to view a package's published version +'npm ls' to inspect current package/dependency versions </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> @@ -50,7 +54,7 @@ This step is skipped if the <code>--force</code> flag is set.</li> <li>Run the <code>preversion</code> script. These scripts have access to the old <code>version</code> in package.json. A typical use would be running your full test suite before deploying. Any files you want added to the commit should be explicitly added using <code>git add</code>.</li> -<li>Bump <code>version</code> in <code>package.json</code> as requested (<code>patch</code>, <code>minor</code>, <code>major</code>, etc). </li> +<li>Bump <code>version</code> in <code>package.json</code> as requested (<code>patch</code>, <code>minor</code>, <code>major</code>, etc).</li> <li>Run the <code>version</code> script. These scripts have access to the new <code>version</code> in package.json (so they can incorporate it into file headers in generated files for example). Again, scripts should explicitly add generated files to the commit using <code>git add</code>.</li> @@ -95,5 +99,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@2.14.7</p> +<p id="footer">npm-version — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-view.html b/deps/npm/html/doc/cli/npm-view.html index 930a299af6..af6d736011 100644 --- a/deps/npm/html/doc/cli/npm-view.html +++ b/deps/npm/html/doc/cli/npm-view.html @@ -11,8 +11,9 @@ <h1><a href="../cli/npm-view.html">npm-view</a></h1> <p>View registry info</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm view [@<scope>/]<name>[@<version>] [<field>[.<subfield>]...] -npm v [@<scope>/]<name>[@<version>] [<field>[.<subfield>]...] +<pre><code>npm view [<@scope>/]<name>[@<version>] [<field>[.<subfield>]...] + +aliases: info, show, v </code></pre><h2 id="description">DESCRIPTION</h2> <p>This command shows data about a package and prints it to the stream referenced by the <code>outfd</code> config, which defaults to stdout.</p> @@ -82,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@2.14.7</p> +<p id="footer">npm-view — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm-whoami.html b/deps/npm/html/doc/cli/npm-whoami.html index 1f25215aeb..2cb374a5ed 100644 --- a/deps/npm/html/doc/cli/npm-whoami.html +++ b/deps/npm/html/doc/cli/npm-whoami.html @@ -11,7 +11,7 @@ <h1><a href="../cli/npm-whoami.html">npm-whoami</a></h1> <p>Display npm username</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm whoami +<pre><code>npm whoami [--registry <registry>] </code></pre><h2 id="description">DESCRIPTION</h2> <p>Print the <code>username</code> config to standard output.</p> <h2 id="see-also">SEE ALSO</h2> @@ -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@2.14.7</p> +<p id="footer">npm-whoami — npm@3.3.6</p> diff --git a/deps/npm/html/doc/cli/npm.html b/deps/npm/html/doc/cli/npm.html index 9fd4df9b2d..7581ad5a29 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>2.14.7</p> +<p>3.3.6</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 @@ -110,7 +110,7 @@ easily by doing <code>npm view npm contributors</code>.</p> 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="mailto:npm-@googlegroups.com">npm-@googlegroups.com</a></li> </ul> <h2 id="bugs">BUGS</h2> <p>When you find issues, please report them:</p> @@ -118,7 +118,7 @@ the issues list or ask on the mailing list.</p> <li>web: <a href="http://github.com/npm/npm/issues">http://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> @@ -154,5 +154,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@2.14.7</p> +<p id="footer">npm — npm@3.3.6</p> |