diff options
| author | Kat Marchán <kzm@sykosomatic.org> | 2017-05-28 21:04:08 -0700 |
|---|---|---|
| committer | Anna Henningsen <anna@addaleax.net> | 2017-05-29 18:06:04 +0200 |
| commit | c58cea5a163cd5d7133e00fdf257325ce3807c09 (patch) | |
| tree | 1b7f97c0474f1990450a54e82b4432ec37de1956 /deps/npm/html | |
| parent | 88fe7e84e56e44a727169c07ee040cbf67f9c0a8 (diff) | |
| download | android-node-v8-c58cea5a163cd5d7133e00fdf257325ce3807c09.tar.gz android-node-v8-c58cea5a163cd5d7133e00fdf257325ce3807c09.tar.bz2 android-node-v8-c58cea5a163cd5d7133e00fdf257325ce3807c09.zip | |
deps: upgrade npm to 5.0.0
PR-URL: https://github.com/nodejs/node/pull/13276
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Diffstat (limited to 'deps/npm/html')
72 files changed, 574 insertions, 296 deletions
diff --git a/deps/npm/html/doc/README.html b/deps/npm/html/doc/README.html index 088f4f5fdb..eb4f72947d 100644 --- a/deps/npm/html/doc/README.html +++ b/deps/npm/html/doc/README.html @@ -126,5 +126,5 @@ will no doubt tell you to put the output in a gist or email.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer"><a href="../doc/README.html">README</a> — npm@5.0.0-beta.56</p> +<p id="footer"><a href="../doc/README.html">README</a> — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-access.html b/deps/npm/html/doc/cli/npm-access.html index e9010b45d1..f015aacdbc 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@5.0.0-beta.56</p> +<p id="footer">npm-access — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-adduser.html b/deps/npm/html/doc/cli/npm-adduser.html index 70a6d56bf7..46385d7295 100644 --- a/deps/npm/html/doc/cli/npm-adduser.html +++ b/deps/npm/html/doc/cli/npm-adduser.html @@ -81,5 +81,5 @@ username/password entry in legacy npm.</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@5.0.0-beta.56</p> +<p id="footer">npm-adduser — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-bin.html b/deps/npm/html/doc/cli/npm-bin.html index 922be47ec5..962a3282d8 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@5.0.0-beta.56</p> +<p id="footer">npm-bin — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-bugs.html b/deps/npm/html/doc/cli/npm-bugs.html index 420f373d82..79e11b018e 100644 --- a/deps/npm/html/doc/cli/npm-bugs.html +++ b/deps/npm/html/doc/cli/npm-bugs.html @@ -55,5 +55,5 @@ a <code>package.json</code> in the current folder and use the <code>name</code> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-bugs — npm@5.0.0-beta.56</p> +<p id="footer">npm-bugs — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-build.html b/deps/npm/html/doc/cli/npm-build.html index 0fc55f149c..ba59bba643 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@5.0.0-beta.56</p> +<p id="footer">npm-build — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-bundle.html b/deps/npm/html/doc/cli/npm-bundle.html index 5971604ba3..8f3510f5b8 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@5.0.0-beta.56</p> +<p id="footer">npm-bundle — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-cache.html b/deps/npm/html/doc/cli/npm-cache.html index 1d78e738c2..fdcf223638 100644 --- a/deps/npm/html/doc/cli/npm-cache.html +++ b/deps/npm/html/doc/cli/npm-cache.html @@ -16,10 +16,10 @@ npm cache add <folder> npm cache add <tarball url> npm cache add <name>@<version> -npm cache ls [<path>] - npm cache clean [<path>] aliases: npm cache clear, npm cache rm + +npm cache verify </code></pre><h2 id="description">DESCRIPTION</h2> <p>Used to add, list, or clean the npm cache folder.</p> <ul> @@ -28,34 +28,39 @@ Add the specified package to the local cache. This command is primarily intended to be used internally by npm, but it can provide a way to add data to the local installation cache explicitly.</p> </li> -<li><p>ls: -Show the data in the cache. Argument is a path to show in the cache -folder. Works a bit like the <code>find</code> program, but limited by the -<code>depth</code> config.</p> -</li> <li><p>clean: -Delete data out of the cache folder. If an argument is provided, then -it specifies a subpath to delete. If no argument is provided, then -the entire cache is deleted.</p> +Delete all data out of the cache folder.</p> +</li> +<li><p>verify: +Verify the contents of the cache folder, garbage collecting any unneeded data, +and verifying the integrity of the cache index and all cached data.</p> </li> </ul> <h2 id="details">DETAILS</h2> -<p>npm stores cache data in the directory specified in <code>npm config get cache</code>. -For each package that is added to the cache, three pieces of information are -stored in <code>{cache}/{name}/{version}</code>:</p> -<ul> -<li>.../package/package.json: -The package.json file, as npm sees it.</li> -<li>.../package.tgz: -The tarball for that version.</li> -</ul> -<p>Additionally, whenever a registry request is made, a <code>.cache.json</code> file -is placed at the corresponding URI, to store the ETag and the requested -data. This is stored in <code>{cache}/{hostname}/{path}/.cache.json</code>.</p> -<p>Commands that make non-essential registry requests (such as <code>search</code> and -<code>view</code>, or the completion scripts) generally specify a minimum timeout. -If the <code>.cache.json</code> file is younger than the specified timeout, then -they do not make an HTTP request to the registry.</p> +<p>npm stores cache data in an opaque directory within the configured <code>cache</code>, +named <code>_cacache</code>. This directory is a <code>cacache</code>-based content-addressable cache +that stores all http request data as well as other package-related data. This +directory is primarily accessed through <code>pacote</code>, the library responsible for +all package fetching as of npm@5.</p> +<p>All data that passes through the cache is fully verified for integrity on both +insertion and extraction. Cache corruption will either trigger an error, or +signal to <code>pacote</code> that the data must be refetched, which it will do +automatically. For this reason, it should never be necessary to clear the cache +for any reason other than reclaiming disk space, thus why <code>clean</code> now requires +<code>--force</code> to run.</p> +<p>There is currently no method exposed through npm to inspect or directly manage +the contents of this cache. In order to access it, <code>cacache</code> must be used +directly.</p> +<p>npm will not remove data by itself: the cache will grow as new packages are +installed.</p> +<h2 id="a-note-about-the-cache-s-design">A NOTE ABOUT THE CACHE'S DESIGN</h2> +<p>The npm cache is strictly a cache: it should not be relied upon as a persistent +and reliable data store for package data. npm makes no guarantee that a +previously-cached piece of data will be available later, and will automatically +delete corrupted contents. The primary guarantee that the cache makes is that, +if it does return data, that data will be exactly the data that was inserted.</p> +<p>To run an offline verification of existing cache contents, use <code>npm cache +verify</code>.</p> <h2 id="configuration">CONFIGURATION</h2> <h3 id="cache">cache</h3> <p>Default: <code>~/.npm</code> on Posix, or <code>%AppData%/npm-cache</code> on Windows.</p> @@ -69,6 +74,8 @@ they do not make an HTTP request to the registry.</p> <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-pack.html">npm-pack(1)</a></li> +<li><a href="https://npm.im/cacache">https://npm.im/cacache</a></li> +<li><a href="https://npm.im/pacote">https://npm.im/pacote</a></li> </ul> </div> @@ -82,5 +89,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@5.0.0-beta.56</p> +<p id="footer">npm-cache — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-completion.html b/deps/npm/html/doc/cli/npm-completion.html index b3515186e0..18d659ea83 100644 --- a/deps/npm/html/doc/cli/npm-completion.html +++ b/deps/npm/html/doc/cli/npm-completion.html @@ -43,5 +43,5 @@ completions based on the arguments.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-completion — npm@5.0.0-beta.56</p> +<p id="footer">npm-completion — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-config.html b/deps/npm/html/doc/cli/npm-config.html index d7a179a749..2ef422bd74 100644 --- a/deps/npm/html/doc/cli/npm-config.html +++ b/deps/npm/html/doc/cli/npm-config.html @@ -67,5 +67,5 @@ global config.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-config — npm@5.0.0-beta.56</p> +<p id="footer">npm-config — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-dedupe.html b/deps/npm/html/doc/cli/npm-dedupe.html index fa1a78e18b..d6ff8ce760 100644 --- a/deps/npm/html/doc/cli/npm-dedupe.html +++ b/deps/npm/html/doc/cli/npm-dedupe.html @@ -61,5 +61,5 @@ result in new modules being installed.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-dedupe — npm@5.0.0-beta.56</p> +<p id="footer">npm-dedupe — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-deprecate.html b/deps/npm/html/doc/cli/npm-deprecate.html index 0fb651b563..6741f7478b 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@5.0.0-beta.56</p> +<p id="footer">npm-deprecate — npm@5.0.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 41def9b127..8fa52c2b33 100644 --- a/deps/npm/html/doc/cli/npm-dist-tag.html +++ b/deps/npm/html/doc/cli/npm-dist-tag.html @@ -86,5 +86,5 @@ begin with a number or the letter <code>v</code>.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-dist-tag — npm@5.0.0-beta.56</p> +<p id="footer">npm-dist-tag — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-docs.html b/deps/npm/html/doc/cli/npm-docs.html index cbf16bb0d0..530a784ed9 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@5.0.0-beta.56</p> +<p id="footer">npm-docs — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-doctor.html b/deps/npm/html/doc/cli/npm-doctor.html index cefa628214..b75fcc5618 100644 --- a/deps/npm/html/doc/cli/npm-doctor.html +++ b/deps/npm/html/doc/cli/npm-doctor.html @@ -103,4 +103,4 @@ cache, you should probably run <code>npm cache clean</code> and reset the cache. <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-doctor — npm@5.0.0-beta.56</p> +<p id="footer">npm-doctor — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-edit.html b/deps/npm/html/doc/cli/npm-edit.html index 784e0fc56c..8860c492ad 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@5.0.0-beta.56</p> +<p id="footer">npm-edit — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-explore.html b/deps/npm/html/doc/cli/npm-explore.html index c25bd194c9..115d43584c 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@5.0.0-beta.56</p> +<p id="footer">npm-explore — npm@5.0.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 922f1dc2bb..a9cb77652b 100644 --- a/deps/npm/html/doc/cli/npm-help-search.html +++ b/deps/npm/html/doc/cli/npm-help-search.html @@ -45,5 +45,5 @@ where the terms were found in the documentation.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-help-search — npm@5.0.0-beta.56</p> +<p id="footer">npm-help-search — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-help.html b/deps/npm/html/doc/cli/npm-help.html index 1ed1413b35..bd72e9471e 100644 --- a/deps/npm/html/doc/cli/npm-help.html +++ b/deps/npm/html/doc/cli/npm-help.html @@ -50,5 +50,5 @@ matches are equivalent to specifying a topic name.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-help — npm@5.0.0-beta.56</p> +<p id="footer">npm-help — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-init.html b/deps/npm/html/doc/cli/npm-init.html index cae2b1c4c4..6f053ddb1b 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@5.0.0-beta.56</p> +<p id="footer">npm-init — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-install-test.html b/deps/npm/html/doc/cli/npm-install-test.html index c8c5bc2d7c..02866f7374 100644 --- a/deps/npm/html/doc/cli/npm-install-test.html +++ b/deps/npm/html/doc/cli/npm-install-test.html @@ -42,5 +42,5 @@ takes exactly the same arguments as <code>npm install</code>.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-install-test — npm@5.0.0-beta.56</p> +<p id="footer">npm-install-test — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-install.html b/deps/npm/html/doc/cli/npm-install.html index 655a7ac69f..55eaabcfd3 100644 --- a/deps/npm/html/doc/cli/npm-install.html +++ b/deps/npm/html/doc/cli/npm-install.html @@ -16,16 +16,19 @@ npm install [<@scope>/]<name> npm install [<@scope>/]<name>@<tag> npm install [<@scope>/]<name>@<version> npm install [<@scope>/]<name>@<version range> +npm install <git-host>:<git-user>/<repo-name> +npm install <git repo url> npm install <tarball file> npm install <tarball url> npm install <folder> alias: npm i -common options: [-S|--save|-D|--save-dev|-O|--save-optional] [-E|--save-exact] [-B|--save-bundle] [--dry-run] +common options: [-P|--save-prod|-D|--save-dev|-O|--save-optional] [-E|--save-exact] [-B|--save-bundle] [--no-save] [--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 -by that. See <a href="../cli/npm-shrinkwrap.html">npm-shrinkwrap(1)</a>.</p> +package has a package-lock or shrinkwrap file, the installation of dependencies +will be driven by that, with an <code>npm-shrinkwrap.json</code> taking precedence if both +files exist. See <a href="../files/package-lock.json.html">package-lock.json(5)</a> and <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 <code><a href="../files/package.json.html">package.json(5)</a></code> file</li> @@ -53,12 +56,16 @@ after packing it up into a tarball (b).</p> <code>devDependencies</code>.</p> </li> <li><p><code>npm install <folder></code>:</p> -<p> Install a package that is sitting in a folder on the filesystem.</p> +<p> Install the package in the directory as a symlink in the current project. + Its dependencies will be installed before it's linked. If <code><folder></code> sits + inside the root of your project, its dependencies may be hoisted to the + toplevel <code>node_modules</code> as they would for other types of dependencies.</p> </li> <li><p><code>npm install <tarball file></code>:</p> <p> Install a package that is sitting on the filesystem. Note: if you just want to link a dev directory into your npm root, you can do this more easily by - using <code>npm link</code>.</p> + using <code>npm link</code>. The filename <em>must</em> use <code>.tar</code>, <code>.tar.gz</code>, or <code>.tgz</code> as + the extension.</p> <p> Example:</p> <pre><code> npm install ./package.tgz </code></pre></li> @@ -68,21 +75,25 @@ 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> [-S|--save|-D|--save-dev|-O|--save-optional]</code>:</p> +<li><p><code>npm install [<@scope>/]<name></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>. 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> In most cases, this will install the version of the modules tagged as + <code>latest</code> on the npm registry.</p> <p> Example:</p> <pre><code> npm install sax -</code></pre><p> <code>npm install</code> takes 3 exclusive, optional flags which save or update - the package version in your main package.json:</p> +</code></pre><p> <code>npm install</code> saves any specified packages into <code>dependencies</code> by default. + Additionally, you can control where and how they get saved with some + additional flags:</p> <ul> -<li><p><code>-S, --save</code>: Package will appear in your <code>dependencies</code>.</p> -</li> +<li><p><code>-P, --save-prod</code>: Package will appear in your <code>dependencies</code>. This is the</p> +<pre><code> default unless `-D` or `-O` are present. +</code></pre></li> <li><p><code>-D, --save-dev</code>: Package will appear in your <code>devDependencies</code>.</p> </li> <li><p><code>-O, --save-optional</code>: Package will appear in your <code>optionalDependencies</code>.</p> +</li> +<li><p><code>--no-save</code>: Prevents saving to <code>dependencies</code>.</p> <p>When using any of the above options to save dependencies to your package.json, there are two additional, optional flags:</p> </li> @@ -91,8 +102,8 @@ exact version rather than using npm's default semver range operator.</p> </li> <li><p><code>-B, --save-bundle</code>: Saved dependencies will also be added to your <code>bundleDependencies</code> list.</p> -<p>Further, if you have an <code>npm-shrinkwrap.json</code> then it will be updated as -well.</p> +<p>Further, if you have an <code>npm-shrinkwrap.json</code> or <code>package-lock.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> @@ -100,13 +111,13 @@ the given scope the default registry is assumed. See <code><a href="../misc/npm- interpret this as a GitHub repository instead, see below. Scopes names must also be followed by a slash.</p> <p>Examples:</p> -<pre><code>npm install sax --save +<pre><code>npm install sax npm install githubname/reponame npm install @myorg/privatepackage npm install node-tap --save-dev npm install dtrace-provider --save-optional -npm install readable-stream --save --save-exact -npm install ansi-regex --save --save-bundle +npm install readable-stream --save-exact +npm install ansi-regex --save-bundle </code></pre></li> </ul> </li> @@ -140,16 +151,24 @@ 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> 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>, <code>git+https</code>, - or <code>git+file</code>. - If no <code><commit-ish></code> is specified, then <code>master</code> is used.</p> -<p> If the repository makes use of submodules, those submodules will - be cloned as well.</p> -<p> The following git environment variables are recognized by npm and will be added - to the environment when running git:</p> +<p> Installs the package from the hosted git provider, cloning it with <code>git</code>. + For a full git remote url, only that URL will be attempted.</p> +<pre><code> <protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>[#<commit-ish> | #semver:<semver>] +</code></pre><p> <code><protocol></code> is one of <code>git</code>, <code>git+ssh</code>, <code>git+http</code>, <code>git+https</code>, or + <code>git+file</code>.</p> +<p> If <code>#<commit-ish></code> is provided, it will be used to clone exactly that + commit. If the commit-ish has the format <code>#semver:<semver></code>, <code><semver></code> can + be any valid semver range or exact version, and npm will look for any tags + or refs matching that range in the remote repository, much as it would for a + registry dependency. If neither <code>#<commit-ish></code> or <code>#semver:<semver></code> is + specified, then <code>master</code> is used.</p> +<p> If the repository makes use of submodules, those submodules will be cloned + as well.</p> +<p> If the package being installed contains a <code>prepare</code> script, its + <code>dependencies</code> and <code>devDependencies</code> will be installed, and the prepare + script will be run, before the package is packaged and installed.</p> +<p> The following git environment variables are recognized by npm and will be + added to the environment when running git:</p> <ul> <li><code>GIT_ASKPASS</code></li> <li><code>GIT_EXEC_PATH</code></li> @@ -161,6 +180,7 @@ fetch the package by name if it is not valid. <p>See the git man page for details.</p> <p>Examples:</p> <pre><code>npm install git+ssh://git@github.com:npm/npm.git#v1.0.27 +npm install git+ssh://git@github.com:npm/npm#semver:^5.0 npm install git+https://isaacs@github.com/npm/npm.git npm install git://github.com/npm/npm.git#v1.0.27 GIT_SSH_COMMAND='ssh -i ~/.ssh/custom_ident' npm install git+ssh://git@github.com:npm/npm.git @@ -172,32 +192,59 @@ GIT_SSH_COMMAND='ssh -i ~/.ssh/custom_ident' npm install git+ssh://git@g <li><p><code>npm install github:<githubname>/<githubrepo>[#<commit-ish>]</code>:</p> <p> Install the package at <code>https://github.com/githubname/githubrepo</code> by attempting to clone it using <code>git</code>.</p> -<p> If you don't specify a <em>commit-ish</em> then <code>master</code> will be used.</p> +<p> If <code>#<commit-ish></code> is provided, it will be used to clone exactly that + commit. If the commit-ish has the format <code>#semver:<semver></code>, <code><semver></code> can + be any valid semver range or exact version, and npm will look for any tags + or refs matching that range in the remote repository, much as it would for a + registry dependency. If neither <code>#<commit-ish></code> or <code>#semver:<semver></code> is + specified, then <code>master</code> is used.</p> +<p> As with regular git dependencies, <code>dependencies</code> and <code>devDependencies</code> will + be installed if the package has a <code>prepare</code> script, before the package is + done installing.</p> <p> Examples:</p> <pre><code> npm install mygithubuser/myproject npm install github:mygithubuser/myproject </code></pre></li> -<li><p><code>npm install gist:[<githubname>/]<gistID>[#<commit-ish>]</code>:</p> +<li><p><code>npm install gist:[<githubname>/]<gistID>[#<commit-ish>|#semver:<semver>]</code>:</p> <p> Install the package at <code>https://gist.github.com/gistID</code> by attempting to clone it using <code>git</code>. The GitHub username associated with the gist is - optional and will not be saved in <code>package.json</code> if <code>-S</code> or <code>--save</code> is used.</p> -<p> If you don't specify a <em>commit-ish</em> then <code>master</code> will be used.</p> + optional and will not be saved in <code>package.json</code>.</p> +<p> As with regular git dependencies, <code>dependencies</code> and <code>devDependencies</code> will + be installed if the package has a <code>prepare</code> script, before the package is + done installing.</p> <p> Example:</p> <pre><code> npm install gist:101a11beef </code></pre></li> <li><p><code>npm install bitbucket:<bitbucketname>/<bitbucketrepo>[#<commit-ish>]</code>:</p> <p> Install the package at <code>https://bitbucket.org/bitbucketname/bitbucketrepo</code> by attempting to clone it using <code>git</code>.</p> -<p> If you don't specify a <em>commit-ish</em> then <code>master</code> will be used.</p> +<p> If <code>#<commit-ish></code> is provided, it will be used to clone exactly that + commit. If the commit-ish has the format <code>#semver:<semver></code>, <code><semver></code> can + be any valid semver range or exact version, and npm will look for any tags + or refs matching that range in the remote repository, much as it would for a + registry dependency. If neither <code>#<commit-ish></code> or <code>#semver:<semver></code> is + specified, then <code>master</code> is used.</p> +<p> As with regular git dependencies, <code>dependencies</code> and <code>devDependencies</code> will + be installed if the package has a <code>prepare</code> script, before the package is + done installing.</p> <p> Example:</p> <pre><code> npm install bitbucket:mybitbucketuser/myproject </code></pre></li> <li><p><code>npm install gitlab:<gitlabname>/<gitlabrepo>[#<commit-ish>]</code>:</p> <p> Install the package at <code>https://gitlab.com/gitlabname/gitlabrepo</code> by attempting to clone it using <code>git</code>.</p> -<p> If you don't specify a <em>commit-ish</em> then <code>master</code> will be used.</p> +<p> If <code>#<commit-ish></code> is provided, it will be used to clone exactly that + commit. If the commit-ish has the format <code>#semver:<semver></code>, <code><semver></code> can + be any valid semver range or exact version, and npm will look for any tags + or refs matching that range in the remote repository, much as it would for a + registry dependency. If neither <code>#<commit-ish></code> or <code>#semver:<semver></code> is + specified, then <code>master</code> is used.</p> +<p> As with regular git dependencies, <code>dependencies</code> and <code>devDependencies</code> will + be installed if the package has a <code>prepare</code> script, before the package is + done installing.</p> <p> Example:</p> <pre><code> npm install gitlab:mygitlabuser/myproject + npm install gitlab:myusr/myproj#semver:^5.0 </code></pre></li> </ul> <p>You may combine multiple arguments, and even multiple types of arguments. @@ -218,7 +265,7 @@ your local <code>node_modules</code> folder with the same layout it uses with th 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 eliminate some deduping.</p> -<p>The <code>--ignore-scripts</code> argument will cause npm to not execute any +<p>The <code>--ignore-scripts</code> argument will cause npm to not execute any scripts defined in the package.json. See <code><a href="../misc/npm-scripts.html">npm-scripts(7)</a></code>.</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, @@ -230,7 +277,7 @@ any binaries the package might contain.</p> <p>The <code>--no-optional</code> argument will prevent optional dependencies from being installed.</p> <p>The <code>--no-shrinkwrap</code> argument, which will ignore an available -shrinkwrap file and use the package.json instead.</p> +package lock or 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 @@ -265,7 +312,9 @@ at the top level because nothing conflicts with it.</p> `-- D@2 +-- D@1 </code></pre><p>Because B's D@1 will be installed in the top level, C now has to install D@2 -privately for itself.</p> +privately for itself. This algorithm is deterministic, but different trees may +be produced if two dependencies are requested for installation in a different +order.</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> @@ -316,5 +365,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@5.0.0-beta.56</p> +<p id="footer">npm-install — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-link.html b/deps/npm/html/doc/cli/npm-link.html index f952876a71..b279ab4d3a 100644 --- a/deps/npm/html/doc/cli/npm-link.html +++ b/deps/npm/html/doc/cli/npm-link.html @@ -74,5 +74,5 @@ include that scope, e.g.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-link — npm@5.0.0-beta.56</p> +<p id="footer">npm-link — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-logout.html b/deps/npm/html/doc/cli/npm-logout.html index 9a1393966a..3ecde84cc3 100644 --- a/deps/npm/html/doc/cli/npm-logout.html +++ b/deps/npm/html/doc/cli/npm-logout.html @@ -51,5 +51,5 @@ it takes precedence.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-logout — npm@5.0.0-beta.56</p> +<p id="footer">npm-logout — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-ls.html b/deps/npm/html/doc/cli/npm-ls.html index 8bd4c70bee..af4103febf 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@5.0.0-beta.56 /path/to/npm +<pre><code>npm@5.0.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@5.0.0-beta.56</p> +<p id="footer">npm-ls — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-outdated.html b/deps/npm/html/doc/cli/npm-outdated.html index e3d7a8540f..7b36dc7f5b 100644 --- a/deps/npm/html/doc/cli/npm-outdated.html +++ b/deps/npm/html/doc/cli/npm-outdated.html @@ -116,5 +116,5 @@ project.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-outdated — npm@5.0.0-beta.56</p> +<p id="footer">npm-outdated — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-owner.html b/deps/npm/html/doc/cli/npm-owner.html index 920f5e5833..aeaa8acb89 100644 --- a/deps/npm/html/doc/cli/npm-owner.html +++ b/deps/npm/html/doc/cli/npm-owner.html @@ -51,5 +51,5 @@ that is not implemented at this time.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-owner — npm@5.0.0-beta.56</p> +<p id="footer">npm-owner — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-pack.html b/deps/npm/html/doc/cli/npm-pack.html index 3956a2a491..d40a92437a 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@5.0.0-beta.56</p> +<p id="footer">npm-pack — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-ping.html b/deps/npm/html/doc/cli/npm-ping.html index 084cfdd834..e9a9f97b20 100644 --- a/deps/npm/html/doc/cli/npm-ping.html +++ b/deps/npm/html/doc/cli/npm-ping.html @@ -32,5 +32,5 @@ <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-ping — npm@5.0.0-beta.56</p> +<p id="footer">npm-ping — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-prefix.html b/deps/npm/html/doc/cli/npm-prefix.html index d3c4f5af94..99dacb6660 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@5.0.0-beta.56</p> +<p id="footer">npm-prefix — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-prune.html b/deps/npm/html/doc/cli/npm-prune.html index 97b39a188e..56e8b8ab29 100644 --- a/deps/npm/html/doc/cli/npm-prune.html +++ b/deps/npm/html/doc/cli/npm-prune.html @@ -40,5 +40,5 @@ negate <code>NODE_ENV</code> being set to <code>production</code>.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-prune — npm@5.0.0-beta.56</p> +<p id="footer">npm-prune — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-publish.html b/deps/npm/html/doc/cli/npm-publish.html index b5f6229484..9b9cca3cb0 100644 --- a/deps/npm/html/doc/cli/npm-publish.html +++ b/deps/npm/html/doc/cli/npm-publish.html @@ -51,6 +51,9 @@ the specified registry.</p> <p>Once a package is published with a given name and version, that specific name and version combination can never be used again, even if it is removed with <a href="../cli/npm-unpublish.html">npm-unpublish(1)</a>.</p> +<p>As of <code>npm@5</code>, both a sha1sum and an integrity field with a sha512sum of the +tarball will be submitted to the registry during publication. Subsequent +installs will use the strongest supported algorithm to verify downloads.</p> <p>For a "dry run" that does everything except actually publishing to the registry, see <code><a href="../cli/npm-pack.html">npm-pack(1)</a></code>, which figures out the files to be included and packs them into a tarball to be uploaded to the registry.</p> @@ -76,5 +79,5 @@ packs them into a tarball to be uploaded to the registry.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-publish — npm@5.0.0-beta.56</p> +<p id="footer">npm-publish — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-rebuild.html b/deps/npm/html/doc/cli/npm-rebuild.html index ac88ecab84..a2a1ad03ab 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@5.0.0-beta.56</p> +<p id="footer">npm-rebuild — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-repo.html b/deps/npm/html/doc/cli/npm-repo.html index ab7311df12..83ec73d5f5 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@5.0.0-beta.56</p> +<p id="footer">npm-repo — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-restart.html b/deps/npm/html/doc/cli/npm-restart.html index 38607f97bb..c4d3296c25 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@5.0.0-beta.56</p> +<p id="footer">npm-restart — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-root.html b/deps/npm/html/doc/cli/npm-root.html index 3376f30e1b..9b115bb003 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@5.0.0-beta.56</p> +<p id="footer">npm-root — npm@5.0.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 9cc5c452f1..07e1c514d6 100644 --- a/deps/npm/html/doc/cli/npm-run-script.html +++ b/deps/npm/html/doc/cli/npm-run-script.html @@ -66,5 +66,5 @@ you will be given a warning to run <code>npm install</code>, just in case you <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-run-script — npm@5.0.0-beta.56</p> +<p id="footer">npm-run-script — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-search.html b/deps/npm/html/doc/cli/npm-search.html index 4989b4760b..02dc30d68e 100644 --- a/deps/npm/html/doc/cli/npm-search.html +++ b/deps/npm/html/doc/cli/npm-search.html @@ -109,5 +109,5 @@ setting.</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@5.0.0-beta.56</p> +<p id="footer">npm-search — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-shrinkwrap.html b/deps/npm/html/doc/cli/npm-shrinkwrap.html index 53592eabe8..a1809977c5 100644 --- a/deps/npm/html/doc/cli/npm-shrinkwrap.html +++ b/deps/npm/html/doc/cli/npm-shrinkwrap.html @@ -9,163 +9,24 @@ <body> <div id="wrapper"> -<h1><a href="../cli/npm-shrinkwrap.html">npm-shrinkwrap</a></h1> <p>Lock down dependency versions</p> +<h1><a href="../cli/npm-shrinkwrap.html">npm-shrinkwrap</a></h1> <p>Lock down dependency versions for publication</p> <h2 id="synopsis">SYNOPSIS</h2> <pre><code>npm shrinkwrap </code></pre><h2 id="description">DESCRIPTION</h2> -<p>This command locks down the versions of a package's dependencies so -that you can control exactly which versions of each dependency will be -used when your package is installed. The <code>package.json</code> file is still -required if you want to use <code>npm install</code>.</p> -<p>By default, <code>npm install</code> recursively installs the target's -dependencies (as specified in <code>package.json</code>), choosing the latest -available version that satisfies the dependency's semver pattern. In -some situations, particularly when shipping software where each change -is tightly managed, it's desirable to fully specify each version of -each dependency recursively so that subsequent builds and deploys do -not inadvertently pick up newer versions of a dependency that satisfy -the semver pattern. Specifying specific semver patterns in each -dependency's <code>package.json</code> would facilitate this, but that's not always -possible or desirable, as when another author owns the npm package. -It's also possible to check dependencies directly into source control, -but that may be undesirable for other reasons.</p> -<p>As an example, consider package A:</p> -<pre><code>{ - "name": "A", - "version": "0.1.0", - "dependencies": { - "B": "<0.1.0" - } -} -</code></pre><p>package B:</p> -<pre><code>{ - "name": "B", - "version": "0.0.1", - "dependencies": { - "C": "<0.1.0" - } -} -</code></pre><p>and package C:</p> -<pre><code>{ - "name": "C", - "version": "0.0.1" -} -</code></pre><p>If these are the only versions of A, B, and C available in the -registry, then a normal <code>npm install A</code> will install:</p> -<pre><code>A@0.1.0 -`-- B@0.0.1 - `-- C@0.0.1 -</code></pre><p>However, if B@0.0.2 is published, then a fresh <code>npm install A</code> will -install:</p> -<pre><code>A@0.1.0 -`-- B@0.0.2 - `-- C@0.0.1 -</code></pre><p>assuming the new version did not modify B's dependencies. Of course, -the new version of B could include a new version of C and any number -of new dependencies. If such changes are undesirable, the author of A -could specify a dependency on B@0.0.1. However, if A's author and B's -author are not the same person, there's no way for A's author to say -that he or she does not want to pull in newly published versions of C -when B hasn't changed at all.</p> -<p>In this case, A's author can run</p> -<pre><code>npm shrinkwrap -</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", - "dependencies": { - "B": { - "version": "0.0.1", - "from": "B@^0.0.1", - "resolved": "https://registry.npmjs.org/B/-/B-0.0.1.tgz", - "dependencies": { - "C": { - "version": "0.0.1", - "from": "org/C#v0.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 <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 fashion.</p> -</li> -</ol> -<p>If <code>preshrinkwrap</code>, <code>shrinkwrap</code> or <code>postshrinkwrap</code> are in the <code>scripts</code> property of the -<code>package.json</code>, they will be executed by running <code>npm shrinkwrap</code>. -<code>preshrinkwrap</code> and <code>shrinkwrap</code> are executed before the shrinkwrap, <code>postshrinkwrap</code> is -executed afterwards. For example to run some postprocessing on the generated file:</p> -<pre><code>"scripts": { "postshrinkwrap": "node fix-shrinkwrap.js" } -</code></pre><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 -<code>package.json</code> file and <code>npm install</code> it.</p> -<h3 id="building-shrinkwrapped-packages">Building shrinkwrapped packages</h3> -<p>To shrinkwrap an existing package:</p> -<ol> -<li>Run <code>npm install</code> in the package root to install the current -versions of all dependencies.</li> -<li>Validate that the package works as expected with these versions.</li> -<li>Run <code>npm shrinkwrap</code>, add <code>npm-shrinkwrap.json</code> to git, and publish -your package.</li> -</ol> -<p>To add or update a dependency in a shrinkwrapped package:</p> -<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 --save</code> or <code>npm install --save-dev</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>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> -<h3 id="other-notes">Other Notes</h3> -<p>A shrinkwrap file must be consistent with the package's <code>package.json</code> -file. <code>npm shrinkwrap</code> will fail if required dependencies are not -already installed, since that would result in a shrinkwrap that -wouldn't actually work. Similarly, the command will fail if there are -extraneous packages (not referenced by <code>package.json</code>), since that would -indicate that <code>package.json</code> is not correct.</p> -<p>Starting with npm v4.0.1, <code>devDependencies</code> are included when you run -<code>npm shrinkwrap</code> and follow the usual rules as to when they're installed. -As of npm v3.10.8, if you run <code>npm install --only=production</code> or -<code>npm install --production</code> with a shrinkwrap including your development -dependencies they won't be installed. Similarly, if the environment -variable <code>NODE_ENV</code> is <code>production</code> then they won't be installed. If you -need compatibility with versions of npm prior to v3.10.8 or otherwise -don't want them in your shrinkwrap you can exclude development -dependencies with: -<code>npm shrinkwrap --only=prod</code> or <code>npm shrinkwrap --production</code>.</p> -<p>If shrinkwrapped package A depends on shrinkwrapped package B, B's -shrinkwrap will not be used as part of the installation of A. However, -because A's shrinkwrap is constructed from a valid installation of B -and recursively specifies all dependencies, the contents of B's -shrinkwrap will implicitly be included in A's shrinkwrap.</p> -<h3 id="caveats">Caveats</h3> -<p>If you wish to lock down the specific bytes included in a package, for -example to have 100% confidence in being able to reproduce a -deployment or build, then you ought to check your dependencies into -source control, or pursue some other mechanism that can verify -contents rather than versions.</p> +<p>This command repurposes <code>package-lock.json</code> into a publishable +<code>npm-shrinkwrap.json</code> or simply creates a new one. The file created and updated +by this command will then take precedence over any other existing or future +<code>package-lock.json</code> files. For a detailed explanation of the design and purpose +of package locks in npm, see <a href="../files/npm-package-locks.html">npm-package-locks(5)</a>.</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-run-script.html">npm-run-script(1)</a></li> <li><a href="../misc/npm-scripts.html">npm-scripts(7)</a></li> <li><a href="../files/package.json.html">package.json(5)</a></li> +<li><a href="../files/npm-package-locks.html">npm-package-locks(5)</a></li> +<li><a href="../files/package-lock.json.html">package-lock.json(5)</a></li> +<li><a href="../files/npm-shrinkwrap.json.html">npm-shrinkwrap.json(5)</a></li> <li><a href="../cli/npm-ls.html">npm-ls(1)</a></li> </ul> @@ -180,5 +41,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@5.0.0-beta.56</p> +<p id="footer">npm-shrinkwrap — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-star.html b/deps/npm/html/doc/cli/npm-star.html index 525da2c5e3..8fce919461 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@5.0.0-beta.56</p> +<p id="footer">npm-star — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-stars.html b/deps/npm/html/doc/cli/npm-stars.html index b702e065e6..db7f2e0633 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@5.0.0-beta.56</p> +<p id="footer">npm-stars — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-start.html b/deps/npm/html/doc/cli/npm-start.html index 81dfed2f63..756bc34e68 100644 --- a/deps/npm/html/doc/cli/npm-start.html +++ b/deps/npm/html/doc/cli/npm-start.html @@ -39,5 +39,5 @@ more details.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-start — npm@5.0.0-beta.56</p> +<p id="footer">npm-start — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-stop.html b/deps/npm/html/doc/cli/npm-stop.html index 864bc7c563..31c18f4ba2 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@5.0.0-beta.56</p> +<p id="footer">npm-stop — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-team.html b/deps/npm/html/doc/cli/npm-team.html index 4587cb2c75..13fd947488 100644 --- a/deps/npm/html/doc/cli/npm-team.html +++ b/deps/npm/html/doc/cli/npm-team.html @@ -67,5 +67,5 @@ use the <code>npm access</code> command to grant or revoke the appropriate permi <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-team — npm@5.0.0-beta.56</p> +<p id="footer">npm-team — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-test.html b/deps/npm/html/doc/cli/npm-test.html index 9befb62594..798519122a 100644 --- a/deps/npm/html/doc/cli/npm-test.html +++ b/deps/npm/html/doc/cli/npm-test.html @@ -36,5 +36,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-test — npm@5.0.0-beta.56</p> +<p id="footer">npm-test — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-uninstall.html b/deps/npm/html/doc/cli/npm-uninstall.html index 55a438b15e..147b6e563e 100644 --- a/deps/npm/html/doc/cli/npm-uninstall.html +++ b/deps/npm/html/doc/cli/npm-uninstall.html @@ -60,5 +60,5 @@ npm uninstall dtrace-provider --save-optional <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-uninstall — npm@5.0.0-beta.56</p> +<p id="footer">npm-uninstall — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-unpublish.html b/deps/npm/html/doc/cli/npm-unpublish.html index 82a74483db..587dad4259 100644 --- a/deps/npm/html/doc/cli/npm-unpublish.html +++ b/deps/npm/html/doc/cli/npm-unpublish.html @@ -51,5 +51,5 @@ contact support@npmjs.com.</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@5.0.0-beta.56</p> +<p id="footer">npm-unpublish — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-update.html b/deps/npm/html/doc/cli/npm-update.html index b5bf305bd5..ee1c38dc69 100644 --- a/deps/npm/html/doc/cli/npm-update.html +++ b/deps/npm/html/doc/cli/npm-update.html @@ -118,5 +118,5 @@ be <em>downgraded</em>.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-update — npm@5.0.0-beta.56</p> +<p id="footer">npm-update — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-version.html b/deps/npm/html/doc/cli/npm-version.html index ab4f3bc1de..00361d5174 100644 --- a/deps/npm/html/doc/cli/npm-version.html +++ b/deps/npm/html/doc/cli/npm-version.html @@ -114,5 +114,5 @@ to the same value as the current version.</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@5.0.0-beta.56</p> +<p id="footer">npm-version — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-view.html b/deps/npm/html/doc/cli/npm-view.html index 3427b1e1ac..9fa968fd63 100644 --- a/deps/npm/html/doc/cli/npm-view.html +++ b/deps/npm/html/doc/cli/npm-view.html @@ -86,5 +86,5 @@ the field name.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-view — npm@5.0.0-beta.56</p> +<p id="footer">npm-view — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm-whoami.html b/deps/npm/html/doc/cli/npm-whoami.html index 3f30703d85..c25ad77e59 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@5.0.0-beta.56</p> +<p id="footer">npm-whoami — npm@5.0.0</p> diff --git a/deps/npm/html/doc/cli/npm.html b/deps/npm/html/doc/cli/npm.html index 48c4396d74..5549514295 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>5.0.0-beta.56</p> +<p>5.0.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 @@ -126,7 +126,7 @@ will no doubt tell you to put the output in a gist or email.</p> <p><a href="http://blog.izs.me/">Isaac Z. Schlueter</a> :: <a href="https://github.com/isaacs/">isaacs</a> :: <a href="http://twitter.com/izs">@izs</a> :: -<a href="mailto:i@izs.me">i@izs.me</a></p> +<a href="mailto:i@izs.me">i@izs.me</a></p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../cli/npm-help.html">npm-help(1)</a></li> @@ -150,5 +150,5 @@ will no doubt tell you to put the output in a gist or email.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm — npm@5.0.0-beta.56</p> +<p id="footer">npm — npm@5.0.0</p> diff --git a/deps/npm/html/doc/files/npm-folders.html b/deps/npm/html/doc/files/npm-folders.html index 795e779c19..4f9656a922 100644 --- a/deps/npm/html/doc/files/npm-folders.html +++ b/deps/npm/html/doc/files/npm-folders.html @@ -182,5 +182,5 @@ cannot be found elsewhere. See <code><a href="../files/package.json.html">packa <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-folders — npm@5.0.0-beta.56</p> +<p id="footer">npm-folders — npm@5.0.0</p> diff --git a/deps/npm/html/doc/files/npm-global.html b/deps/npm/html/doc/files/npm-global.html index 795e779c19..4f9656a922 100644 --- a/deps/npm/html/doc/files/npm-global.html +++ b/deps/npm/html/doc/files/npm-global.html @@ -182,5 +182,5 @@ cannot be found elsewhere. See <code><a href="../files/package.json.html">packa <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-folders — npm@5.0.0-beta.56</p> +<p id="footer">npm-folders — npm@5.0.0</p> diff --git a/deps/npm/html/doc/files/npm-json.html b/deps/npm/html/doc/files/npm-json.html index bf65afd5e5..7d6ed1c78a 100644 --- a/deps/npm/html/doc/files/npm-json.html +++ b/deps/npm/html/doc/files/npm-json.html @@ -586,5 +586,5 @@ ignored.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">package.json — npm@5.0.0-beta.56</p> +<p id="footer">package.json — npm@5.0.0</p> diff --git a/deps/npm/html/doc/files/npm-package-locks.html b/deps/npm/html/doc/files/npm-package-locks.html new file mode 100644 index 0000000000..7f8851781b --- /dev/null +++ b/deps/npm/html/doc/files/npm-package-locks.html @@ -0,0 +1,148 @@ +<!doctype html> +<html> + <title>npm-package-locks</title> + <meta charset="utf-8"> + <link rel="stylesheet" type="text/css" href="../../static/style.css"> + <link rel="canonical" href="https://www.npmjs.org/doc/files/npm-package-locks.html"> + <script async=true src="../../static/toc.js"></script> + + <body> + <div id="wrapper"> + +<h1><a href="../files/npm-package-locks.html">npm-package-locks</a></h1> <p>An explanation of npm lockfiles</p> +<h2 id="description">DESCRIPTION</h2> +<p>Conceptually, the "input" to <a href="../cli/npm-install.html">npm-install(1)</a> is a <a href="../files/package.json.html">package.json(5)</a>, while its +"output" is a fully-formed <code>node_modules</code> tree: a representation of the +dependencies you declared. In an ideal world, npm would work like a pure +function: the same <code>package.json</code> should produce the exact same <code>node_modules</code> +tree, any time. In some cases, this is indeed true. But in many others, npm is +unable to do this. There are multiple reasons for this:</p> +<ul> +<li><p>different versions of npm (or other package managers) may have been used to install a package, each using slightly different installation algorithms.</p> +</li> +<li><p>a new version of a direct semver-range package may have been published since the last time your packages were installed, and thus a newer version will be used.</p> +</li> +<li><p>A dependency of one of your dependencies may have published a new version, which will update even if you used pinned dependency specifiers (<code>1.2.3</code> instead of <code>^1.2.3</code>)</p> +</li> +<li><p>The registry you installed from is no longer available, or allows mutation of versions (unlike the primary npm registry), and a different version of a package exists under the same version number now.</p> +</li> +</ul> +<p>As an example, consider package A:</p> +<pre><code>{ + "name": "A", + "version": "0.1.0", + "dependencies": { + "B": "<0.1.0" + } +} +</code></pre><p>package B:</p> +<pre><code>{ + "name": "B", + "version": "0.0.1", + "dependencies": { + "C": "<0.1.0" + } +} +</code></pre><p>and package C:</p> +<pre><code>{ + "name": "C", + "version": "0.0.1" +} +</code></pre><p>If these are the only versions of A, B, and C available in the +registry, then a normal <code>npm install A</code> will install:</p> +<pre><code>A@0.1.0 +`-- B@0.0.1 + `-- C@0.0.1 +</code></pre><p>However, if B@0.0.2 is published, then a fresh <code>npm install A</code> will +install:</p> +<pre><code>A@0.1.0 +`-- B@0.0.2 + `-- C@0.0.1 +</code></pre><p>assuming the new version did not modify B's dependencies. Of course, +the new version of B could include a new version of C and any number +of new dependencies. If such changes are undesirable, the author of A +could specify a dependency on B@0.0.1. However, if A's author and B's +author are not the same person, there's no way for A's author to say +that he or she does not want to pull in newly published versions of C +when B hasn't changed at all.</p> +<p>To prevent this potential issue, npm uses <a href="../files/package-lock.json.html">package-lock.json(5)</a> or, if present, +n<a href="../files/pm-shrinkwrap.json.html">pm-shrinkwrap.json(5)</a>. These files are called package locks, or lockfiles.</p> +<p>Whenever you run <code>npm install</code>, npm generates or updates your package lock, +which will look something like this:</p> +<pre><code>{ + "name": "A", + "version": "0.1.0", + ...metadata fields... + "dependencies": { + "B": { + "version": "0.0.1", + "resolved": "https://registry.npmjs.org/B/-/B-0.0.1.tgz", + "integrity": "sha512-DeAdb33F+" + "dependencies": { + "C": { + "version": "git://github.com/org/C.git#5c380ae319fc4efe9e7f2d9c78b0faa588fd99b4" + } + } + } + } +} +</code></pre><p>This file describes an <em>exact</em>, and more importantly <em>reproducible</em> +<code>node_modules</code> tree. Once it's present, and future installation will base its +work off this file, instead of recalculating dependency versions off +p<a href="../files/ackage.json.html">ackage.json(5)</a>.</p> +<p>The presence of a package lock changes the installation behavior such that:</p> +<ol> +<li><p>The module tree described by the package lock 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 +fashion.</p> +</li> +</ol> +<p>If <code>preshrinkwrap</code>, <code>shrinkwrap</code> or <code>postshrinkwrap</code> are in the <code>scripts</code> +property of the <code>package.json</code>, they will be executed in order. <code>preshrinkwrap</code> +and <code>shrinkwrap</code> are executed before the shrinkwrap, <code>postshrinkwrap</code> is +executed afterwards. These scripts run for both <code>package-lock.json</code> and +<code>npm-shrinkwrap.json</code>. For example to run some postprocessing on the generated +file:</p> +<pre><code>"scripts": { + "postshrinkwrap": "json -I -e \"this.myMetadata = $MY_APP_METADATA\"" +} +</code></pre><h3 id="using-locked-packages">Using locked packages</h3> +<p>Using a locked package is no different than using any package without a package +lock: any commands that update <code>node_modules</code> and/or <code>package.json</code>'s +dependencies will automatically sync the existing lockfile. This includes <code>npm +install</code>, <code>npm rm</code>, <code>npm update</code>, etc. To prevent this update from happening, +you can use the <code>--no-save</code> option to prevent saving altogether, or +<code>--no-shrinkwrap</code> to allow <code>package.json</code> to be updated while leaving +<code>package-lock.json</code> or <code>npm-shrinkwrap.json</code> intact.</p> +<p>It is highly recommended you commit the generated package lock to source +control: this will allow anyone else on your team, your deployments, your +CI/continuous integration, and anyone else who runs <code>npm install</code> in your +package source to get the exact same dependency tree that you were developing +on. Additionally, the diffs from these changes are human-readable and will +inform you of any changes npm has made to your <code>node_modules</code>, so you can notice +if any transitive dependencies were updated, hoisted, etc.</p> +<h2 id="see-also">SEE ALSO</h2> +<ul> +<li><a href="https://medium.com/@sdboyer/so-you-want-to-write-a-package-manager-4ae9c17d9527">https://medium.com/@sdboyer/so-you-want-to-write-a-package-manager-4ae9c17d9527</a></li> +<li><a href="../files/package.json.html">package.json(5)</a></li> +<li><a href="../files/package-lock.json.html">package-lock.json(5)</a></li> +<li><a href="../files/npm-shrinkwrap.json.html">npm-shrinkwrap.json(5)</a></li> +<li><a href="../cli/npm-shrinkwrap.html">npm-shrinkwrap(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-package-locks — npm@5.0.0</p> diff --git a/deps/npm/html/doc/files/npm-shrinkwrap.json.html b/deps/npm/html/doc/files/npm-shrinkwrap.json.html new file mode 100644 index 0000000000..3498af7921 --- /dev/null +++ b/deps/npm/html/doc/files/npm-shrinkwrap.json.html @@ -0,0 +1,45 @@ +<!doctype html> +<html> + <title>npm-shrinkwrap.json</title> + <meta charset="utf-8"> + <link rel="stylesheet" type="text/css" href="../../static/style.css"> + <link rel="canonical" href="https://www.npmjs.org/doc/files/npm-shrinkwrap.json.html"> + <script async=true src="../../static/toc.js"></script> + + <body> + <div id="wrapper"> + +<h1><a href="../files/npm-shrinkwrap.json.html">npm-shrinkwrap.json</a></h1> <p>A publishable lockfile</p> +<h2 id="description">DESCRIPTION</h2> +<p><code>npm-shrinkwrap.json</code> is a file created by <a href="../cli/npm-shrinkwrap.html">npm-shrinkwrap(1)</a>. It is identical to +<code>package-lock.json</code>, with one major caveat: Unlike <code>package-lock.json</code>, +<code>npm-shrinwkrap.json</code> may be included when publishing a package.</p> +<p>The recommended use-case for <code>npm-shrinkwrap.json</code> is applications deployed +through the publishing process on the registry: for example, daemons and +command-line tools intended as global installs or <code>devDependencies</code>. It's +strongly discouraged for library authors to publish this file, since that would +prevent end users from having control over transitive dependency updates.</p> +<p>Additionally, if both <code>package-lock.json</code> and <code>npm-shrinwkrap.json</code> are present +in a package root, <code>package-lock.json</code> will be ignored in favor of this file.</p> +<p>For full details and description of the <code>npm-shrinkwrap.json</code> file format, refer +to the manual page for <a href="../files/package-lock.json.html">package-lock.json(5)</a>.</p> +<h2 id="see-also">SEE ALSO</h2> +<ul> +<li><a href="../cli/npm-shrinkwrap.html">npm-shrinkwrap(1)</a></li> +<li><a href="../files/package-lock.json.html">package-lock.json(5)</a></li> +<li><a href="../files/package.json.html">package.json(5)</a></li> +<li><a href="../cli/npm-install.html">npm-install(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-shrinkwrap.json — npm@5.0.0</p> diff --git a/deps/npm/html/doc/files/npmrc.html b/deps/npm/html/doc/files/npmrc.html index 33b683292f..ef6d01b611 100644 --- a/deps/npm/html/doc/files/npmrc.html +++ b/deps/npm/html/doc/files/npmrc.html @@ -85,5 +85,5 @@ manner.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npmrc — npm@5.0.0-beta.56</p> +<p id="footer">npmrc — npm@5.0.0</p> diff --git a/deps/npm/html/doc/files/package-lock.json.html b/deps/npm/html/doc/files/package-lock.json.html new file mode 100644 index 0000000000..57423161bd --- /dev/null +++ b/deps/npm/html/doc/files/package-lock.json.html @@ -0,0 +1,127 @@ +<!doctype html> +<html> + <title>package-lock.json</title> + <meta charset="utf-8"> + <link rel="stylesheet" type="text/css" href="../../static/style.css"> + <link rel="canonical" href="https://www.npmjs.org/doc/files/package-lock.json.html"> + <script async=true src="../../static/toc.js"></script> + + <body> + <div id="wrapper"> + +<h1><a href="../files/package-lock.json.html">package-lock.json</a></h1> <p>A manifestation of the manifest</p> +<h2 id="description">DESCRIPTION</h2> +<p><code>package-lock.json</code> is automatically generated for any operations where npm +modifies either the <code>node_modules</code> tree, or <code>package.json</code>. It describes the +exact tree that was generated, such that subsequent installs are able to +generate identical trees, regardless of intermediate dependency updates.</p> +<p>This file is intended to be committed into source repositories, and serves +various purposes:</p> +<ul> +<li><p>Describe a single representation of a dependency tree such that teammates, deployments, and continuous integration are guaranteed to install exactly the same dependencies.</p> +</li> +<li><p>Provide a facility for users to "time-travel" to previous states of <code>node_modules</code> without having to commit the directory itself.</p> +</li> +<li><p>To facilitate greater visibility of tree changes through readable source control diffs.</p> +</li> +<li><p>And optimize the installation process by allowing npm to skip repeated metadata resolutions for previously-installed packages.</p> +</li> +</ul> +<p>One key detail about <code>package-lock.json</code> is that it cannot be published, and it +will be ignored if found in any place other than the toplevel package. It shares +a format with <a href="../files/npm-shrinkwrap.json.html">npm-shrinkwrap.json(5)</a>, which is essentially the same file, but +allows publication. This is not recommended unless deploying a CLI tool or +otherwise using the publication process for producing production packages.</p> +<p>If both <code>package-lock.json</code> and <code>npm-shrinkwrap.json</code> are present in the root of +a package, <code>package-lock.json</code> will be completely ignored.</p> +<h2 id="file-format">FILE FORMAT</h2> +<h3 id="name">name</h3> +<p>The name of the package this is a package-lock for. This must match what's in +<code>package.json</code>.</p> +<h3 id="version">version</h3> +<p>The version of the package this is a package-lock for. This must match what's in +<code>package.json</code>.</p> +<h3 id="lockfileversion">lockfileVersion</h3> +<p>An integer version, starting at <code>1</code> with the version number of this document +whose semantics were used when generating this <code>package-lock.json</code>.</p> +<h3 id="packageintegrity">packageIntegrity</h3> +<p>This is a <a href="https://w3c.github.io/webappsec/specs/subresourceintegrity/">subresource +integrity</a> value +created from the <code>pacakge.json</code>. No preprocessing of the <code>package.json</code> should +be done. Subresource integrity strings can be produced by modules like +<a href="https://www.npmjs.com/package/ssri"><code>ssri</code></a>.</p> +<h3 id="preservesymlinks">preserveSymlinks</h3> +<p>Indicates that the install was done with the environment variable +<code>NODE_PRESERVE_SYMLINKS</code> enabled. The installer should insist that the value of +this property match that environment variable.</p> +<h3 id="dependencies">dependencies</h3> +<p>A mapping of package name to dependency object. Dependency objects have the +following properties:</p> +<h4 id="version">version</h4> +<p>This is a specifier that uniquely identifies this package and should be +usable in fetching a new copy of it.</p> +<ul> +<li>bundled dependencies: Regardless of source, this is a version number that is purely for informational purposes.</li> +<li>registry sources: This is a version number. (eg, <code>1.2.3</code>)</li> +<li>git sources: This is a git specifier with resolved committish. (eg, <code>git+https://example.com/foo/bar#115311855adb0789a0466714ed48a1499ffea97e</code>)</li> +<li>http tarball sources: This is the URL of the tarball. (eg, <code>https://example.com/example-1.3.0.tgz</code>)</li> +<li>local tarball sources: This is the file URL of the tarball. (eg <code>file:///opt/storage/example-1.3.0.tgz</code>)</li> +<li>local link sources: This is the file URL of the link. (eg <code>file:libs/our-module</code>)</li> +</ul> +<h4 id="integrity">integrity</h4> +<p>This is a <a href="https://w3c.github.io/webappsec/specs/subresourceintegrity/">Standard Subresource +Integrity</a> for this +resource.</p> +<ul> +<li>For bundled dependencies this is not included, regardless of source.</li> +<li>For registry sources, this is the <code>integrity</code> that the registry provided, or if one wasn't provided the SHA1 in <code>shasum</code>.</li> +<li>For git sources this is the specific commit hash we cloned from.</li> +<li>For remote tarball sources this is an integrity based on a SHA512 of +the file.</li> +<li>For local tarball sources: This is an integrity field based on the SHA512 of the file.</li> +</ul> +<h4 id="resolved">resolved</h4> +<ul> +<li>For bundled dependencies this is not included, regardless of source.</li> +<li>For registry sources this is path of the tarball relative to the registry +URL. If the tarball URL isn't on the same server as the registry URL then +this is a complete URL.</li> +</ul> +<h4 id="bundled">bundled</h4> +<p>If true, this is the bundled dependency and will be installed by the parent +module. When installing, this module will be extracted from the parent +module during the extract phase, not installed as a separate dependency.</p> +<h4 id="dev">dev</h4> +<p>If true then this dependency is either a development dependency ONLY of the +top level module or a transitive dependency of one. This is false for +dependencies that are both a development dependency of the top level and a +transitive dependency of a non-development dependency of the top level.</p> +<h4 id="optional">optional</h4> +<p>If true then this dependency is either an optional dependency ONLY of the +top level module or a transitive dependency of one. This is false for +dependencies that are both an optional dependency of the top level and a +transitive dependency of a non-optional dependency of the top level.</p> +<p>All optional dependencies should be included even if they're uninstallable +on the current platform.</p> +<h4 id="dependencies">dependencies</h4> +<p>The dependencies of this dependency, exactly as at the top level.</p> +<h2 id="see-also">SEE ALSO</h2> +<ul> +<li><a href="../cli/npm-shrinkwrap.html">npm-shrinkwrap(1)</a></li> +<li><a href="../files/package-lock.json.html">package-lock.json(5)</a></li> +<li><a href="../files/package.json.html">package.json(5)</a></li> +<li><a href="../cli/npm-install.html">npm-install(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">package-lock.json — npm@5.0.0</p> diff --git a/deps/npm/html/doc/files/package.json.html b/deps/npm/html/doc/files/package.json.html index bf65afd5e5..7d6ed1c78a 100644 --- a/deps/npm/html/doc/files/package.json.html +++ b/deps/npm/html/doc/files/package.json.html @@ -586,5 +586,5 @@ ignored.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">package.json — npm@5.0.0-beta.56</p> +<p id="footer">package.json — npm@5.0.0</p> diff --git a/deps/npm/html/doc/index.html b/deps/npm/html/doc/index.html index 39f5d8e028..75891616b8 100644 --- a/deps/npm/html/doc/index.html +++ b/deps/npm/html/doc/index.html @@ -91,7 +91,7 @@ <h3 id="npm-search-1-"><a href="cli/npm-search.html">npm-search(1)</a></h3> <p>Search for packages</p> <h3 id="npm-shrinkwrap-1-"><a href="cli/npm-shrinkwrap.html">npm-shrinkwrap(1)</a></h3> -<p>Lock down dependency versions</p> +<p>Lock down dependency versions for publication</p> <h3 id="npm-star-1-"><a href="cli/npm-star.html">npm-star(1)</a></h3> <p>Mark your favorite packages</p> <h3 id="npm-stars-1-"><a href="cli/npm-stars.html">npm-stars(1)</a></h3> @@ -122,8 +122,14 @@ <p>File system structures npm uses</p> <h3 id="npm-folders-5-"><a href="files/npm-folders.html">npm-folders(5)</a></h3> <p>Folder Structures Used by npm</p> +<h3 id="npm-package-locks-5-"><a href="files/npm-package-locks.html">npm-package-locks(5)</a></h3> +<p>An explanation of npm lockfiles</p> +<h3 id="npm-shrinkwrap-json-5-"><a href="files/npm-shrinkwrap.json.html">npm-shrinkwrap.json(5)</a></h3> +<p>A publishable lockfile</p> <h3 id="npmrc-5-"><a href="files/npmrc.html">npmrc(5)</a></h3> <p>The npm config files</p> +<h3 id="package-lock-json-5-"><a href="files/package-lock.json.html">package-lock.json(5)</a></h3> +<p>A manifestation of the manifest</p> <h3 id="package-json-5-"><a href="files/package.json.html">package.json(5)</a></h3> <p>Specifics of npm's package.json handling</p> <h2 id="misc">Misc</h2> @@ -162,5 +168,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@5.0.0-beta.56</p> +<p id="footer">npm-index — npm@5.0.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 77e6735e7d..0048979e90 100644 --- a/deps/npm/html/doc/misc/npm-coding-style.html +++ b/deps/npm/html/doc/misc/npm-coding-style.html @@ -153,5 +153,5 @@ set to anything."</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-coding-style — npm@5.0.0-beta.56</p> +<p id="footer">npm-coding-style — npm@5.0.0</p> diff --git a/deps/npm/html/doc/misc/npm-config.html b/deps/npm/html/doc/misc/npm-config.html index 78e9569e5b..bed7aa0736 100644 --- a/deps/npm/html/doc/misc/npm-config.html +++ b/deps/npm/html/doc/misc/npm-config.html @@ -61,6 +61,7 @@ internal to npm, and are defaults if nothing else is specified.</p> <li><code>-f</code>: <code>--force</code></li> <li><code>-desc</code>: <code>--description</code></li> <li><code>-S</code>: <code>--save</code></li> +<li><code>-P</code>: <code>--save-prod</code></li> <li><code>-D</code>: <code>--save-dev</code></li> <li><code>-O</code>: <code>--save-optional</code></li> <li><code>-B</code>: <code>--save-bundle</code></li> @@ -586,6 +587,14 @@ installed.</p> <p>Attempt to install packages in the <code>optionalDependencies</code> object. Note that if these packages fail to install, the overall installation process is not aborted.</p> +<h3 id="package-lock">package-lock</h3> +<ul> +<li>Default: true</li> +<li>Type: Boolean</li> +</ul> +<p>If set to false, then ignore <code>package-lock.json</code> files when installing. This +will also prevent <em>writing</em> <code>package-lock.json</code> if <code>save</code> is true.</p> +<p>This option is an alias for <code>--shrinkwrap</code>.</p> <h3 id="parseable">parseable</h3> <ul> <li>Default: false</li> @@ -689,6 +698,16 @@ object.</p> <code>bundleDependencies</code> list.</p> <p>When used with the <code>npm rm</code> command, it removes it from the bundledDependencies list.</p> +<h3 id="save-prod">save-prod</h3> +<ul> +<li>Default: false</li> +<li>Type: Boolean</li> +</ul> +<p>Makes sure that a package will be saved into <code>dependencies</code> specifically. This +is useful if a package already exists in <code>devDependencies</code> or +<code>optionalDependencies</code>, but you want to move it to be a production dep. This is +also the default behavior if <code>--save</code> is true, and neither <code>--save-dev</code> or +<code>--save-optional</code> are true.</p> <h3 id="save-dev">save-dev</h3> <ul> <li>Default: false</li> @@ -800,8 +819,9 @@ Windows</li> <li>Default: true</li> <li>Type: Boolean</li> </ul> -<p>If set to false, then ignore <code>npm-shrinkwrap.json</code> files when -installing.</p> +<p>If set to false, then ignore <code>npm-shrinkwrap.json</code> files when installing. This +will also prevent <em>writing</em> <code>npm-shrinkwrap.json</code> if <code>save</code> is true.</p> +<p>This option is an alias for <code>--package-lock</code>.</p> <h3 id="sign-git-tag">sign-git-tag</h3> <ul> <li>Default: false</li> @@ -961,5 +981,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@5.0.0-beta.56</p> +<p id="footer">npm-config — npm@5.0.0</p> diff --git a/deps/npm/html/doc/misc/npm-developers.html b/deps/npm/html/doc/misc/npm-developers.html index 52d1464490..d87e8c05fc 100644 --- a/deps/npm/html/doc/misc/npm-developers.html +++ b/deps/npm/html/doc/misc/npm-developers.html @@ -194,5 +194,5 @@ from a fresh checkout.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-developers — npm@5.0.0-beta.56</p> +<p id="footer">npm-developers — npm@5.0.0</p> diff --git a/deps/npm/html/doc/misc/npm-disputes.html b/deps/npm/html/doc/misc/npm-disputes.html index f57404e375..e5d95529e6 100644 --- a/deps/npm/html/doc/misc/npm-disputes.html +++ b/deps/npm/html/doc/misc/npm-disputes.html @@ -20,7 +20,7 @@ Conduct.</p> <h2 id="tl-dr">TL;DR</h2> <ol> <li>Get the author email with <code>npm owner ls <pkgname></code></li> -<li>Email the author, CC <a href="mailto:support@npmjs.com">support@npmjs.com</a></li> +<li>Email the author, CC <a href="mailto:support@npmjs.com">support@npmjs.com</a></li> <li>After a few weeks, if there's no resolution, we'll sort it out.</li> </ol> <p>Don't squat on package names. Publish code or move out of the way.</p> @@ -55,12 +55,12 @@ because Yusuf's <code>foo</code> is in the way.</p> </li> <li>Alice emails Yusuf, explaining the situation <strong>as respectfully as possible</strong>, and what she would like to do with the module name. She adds the npm support -staff <a href="mailto:support@npmjs.com">support@npmjs.com</a> to the CC list of the email. Mention in the email +staff <a href="mailto:support@npmjs.com">support@npmjs.com</a> to the CC list of the email. Mention in the email that Yusuf can run npm owner <code>add alice foo</code> to add Alice as an owner of the foo package.</li> <li>After a reasonable amount of time, if Yusuf has not responded, or if Yusuf and Alice can't come to any sort of resolution, email support -<a href="mailto:support@npmjs.com">support@npmjs.com</a> and we'll sort it out. ("Reasonable" is usually at least +<a href="mailto:support@npmjs.com">support@npmjs.com</a> and we'll sort it out. ("Reasonable" is usually at least 4 weeks.)</li> </ol> <h2 id="reasoning">REASONING</h2> @@ -96,12 +96,12 @@ application database or otherwise putting non-packagey things into it.</li> <a href="https://www.npmjs.com/policies/conduct">Code of Conduct</a> such as hateful language, pornographic content, or harassment.</li> </ol> -<p>If you see bad behavior like this, please report it to <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> right +<p>If you see bad behavior like this, please report it to <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> right away. <strong>You are never expected to resolve abusive behavior on your own. We are here to help.</strong></p> <h2 id="trademarks">TRADEMARKS</h2> <p>If you think another npm publisher is infringing your trademark, such as by -using a confusingly similar package name, email <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> with a link to +using a confusingly similar package name, email <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> with a link to the package or user account on <a href="https://npmjs.com">https://npmjs.com</a>. Attach a copy of your trademark registration certificate.</p> <p>If we see that the package's publisher is intentionally misleading others by @@ -134,5 +134,5 @@ License.</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-disputes — npm@5.0.0-beta.56</p> +<p id="footer">npm-disputes — npm@5.0.0</p> diff --git a/deps/npm/html/doc/misc/npm-index.html b/deps/npm/html/doc/misc/npm-index.html index c2bd8c3574..75956cc368 100644 --- a/deps/npm/html/doc/misc/npm-index.html +++ b/deps/npm/html/doc/misc/npm-index.html @@ -91,7 +91,7 @@ <h3 id="npm-search-1-"><a href="../cli/npm-search.html">npm-search(1)</a></h3> <p>Search for packages</p> <h3 id="npm-shrinkwrap-1-"><a href="../cli/npm-shrinkwrap.html">npm-shrinkwrap(1)</a></h3> -<p>Lock down dependency versions</p> +<p>Lock down dependency versions for publication</p> <h3 id="npm-star-1-"><a href="../cli/npm-star.html">npm-star(1)</a></h3> <p>Mark your favorite packages</p> <h3 id="npm-stars-1-"><a href="../cli/npm-stars.html">npm-stars(1)</a></h3> @@ -122,8 +122,14 @@ <p>File system structures npm uses</p> <h3 id="npm-folders-5-"><a href="../files/npm-folders.html">npm-folders(5)</a></h3> <p>Folder Structures Used by npm</p> +<h3 id="npm-package-locks-5-"><a href="../files/npm-package-locks.html">npm-package-locks(5)</a></h3> +<p>An explanation of npm lockfiles</p> +<h3 id="npm-shrinkwrap-json-5-"><a href="../files/npm-shrinkwrap.json.html">npm-shrinkwrap.json(5)</a></h3> +<p>A publishable lockfile</p> <h3 id="npmrc-5-"><a href="../files/npmrc.html">npmrc(5)</a></h3> <p>The npm config files</p> +<h3 id="package-lock-json-5-"><a href="../files/package-lock.json.html">package-lock.json(5)</a></h3> +<p>A manifestation of the manifest</p> <h3 id="package-json-5-"><a href="../files/package.json.html">package.json(5)</a></h3> <p>Specifics of npm's package.json handling</p> <h2 id="misc">Misc</h2> @@ -162,5 +168,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@5.0.0-beta.56</p> +<p id="footer">npm-index — npm@5.0.0</p> diff --git a/deps/npm/html/doc/misc/npm-orgs.html b/deps/npm/html/doc/misc/npm-orgs.html index 75c1850cc2..1c769d1495 100644 --- a/deps/npm/html/doc/misc/npm-orgs.html +++ b/deps/npm/html/doc/misc/npm-orgs.html @@ -86,5 +86,5 @@ <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-orgs — npm@5.0.0-beta.56</p> +<p id="footer">npm-orgs — npm@5.0.0</p> diff --git a/deps/npm/html/doc/misc/npm-registry.html b/deps/npm/html/doc/misc/npm-registry.html index 99e4d75926..aca3dc550c 100644 --- a/deps/npm/html/doc/misc/npm-registry.html +++ b/deps/npm/html/doc/misc/npm-registry.html @@ -90,5 +90,5 @@ effectively implement the entire CouchDB API anyway.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-registry — npm@5.0.0-beta.56</p> +<p id="footer">npm-registry — npm@5.0.0</p> diff --git a/deps/npm/html/doc/misc/npm-scope.html b/deps/npm/html/doc/misc/npm-scope.html index 481e367a0d..f15285ba78 100644 --- a/deps/npm/html/doc/misc/npm-scope.html +++ b/deps/npm/html/doc/misc/npm-scope.html @@ -99,5 +99,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@5.0.0-beta.56</p> +<p id="footer">npm-scope — npm@5.0.0</p> diff --git a/deps/npm/html/doc/misc/npm-scripts.html b/deps/npm/html/doc/misc/npm-scripts.html index be6269f081..976695a05c 100644 --- a/deps/npm/html/doc/misc/npm-scripts.html +++ b/deps/npm/html/doc/misc/npm-scripts.html @@ -15,14 +15,20 @@ following scripts:</p> <ul> <li>prepublish: -Run BEFORE the package is published. (Also run on local <code>npm -install</code> without any arguments. See below.)</li> +Run BEFORE the package is packed and published, as well as on local <code>npm +install</code> without any arguments. (See below)</li> <li>prepare: -Run both BEFORE the package is published, and on local <code>npm -install</code> without any arguments. (See below.) This is run +Run both BEFORE the package is packed and published, and on local <code>npm +install</code> without any arguments (See below). This is run AFTER <code>prepublish</code>, but BEFORE <code>prepublishOnly</code>.</li> <li>prepublishOnly: -Run BEFORE the package is published. (See below.)</li> +Run BEFORE the package is prepared and packed, ONLY on <code>npm publish</code>. (See +below.)</li> +<li>prepack: +run BEFORE a tarball is packed (on <code>npm pack</code>, <code>npm publish</code>, and when +installing git dependencies)</li> +<li>postpack: +Run AFTER the tarball has been generated and moved to its final destination.</li> <li>publish, postpublish: Run AFTER the package is published.</li> <li>preinstall: @@ -237,5 +243,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@5.0.0-beta.56</p> +<p id="footer">npm-scripts — npm@5.0.0</p> diff --git a/deps/npm/html/doc/misc/removing-npm.html b/deps/npm/html/doc/misc/removing-npm.html index 532c44588d..8a7a51e4b0 100644 --- a/deps/npm/html/doc/misc/removing-npm.html +++ b/deps/npm/html/doc/misc/removing-npm.html @@ -57,5 +57,5 @@ modules. To track those down, you can do the following:</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">removing-npm — npm@5.0.0-beta.56</p> +<p id="footer">removing-npm — npm@5.0.0</p> diff --git a/deps/npm/html/doc/misc/semver.html b/deps/npm/html/doc/misc/semver.html index 80827586f1..5a8b556bca 100644 --- a/deps/npm/html/doc/misc/semver.html +++ b/deps/npm/html/doc/misc/semver.html @@ -325,5 +325,5 @@ range, use the <code>satisfies(version, range)</code> function.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">semver — npm@5.0.0-beta.56</p> +<p id="footer">semver — npm@5.0.0</p> |