diff options
Diffstat (limited to 'deps/npm/html/doc')
78 files changed, 585 insertions, 218 deletions
diff --git a/deps/npm/html/doc/README.html b/deps/npm/html/doc/README.html index 48f8433f62..f7a482f465 100644 --- a/deps/npm/html/doc/README.html +++ b/deps/npm/html/doc/README.html @@ -15,8 +15,8 @@ <p>This is just enough info to get you up and running.</p> <p>Much more info available via <code>npm help</code> once it's installed.</p> <h2 id="important">IMPORTANT</h2> -<p><strong>You need node v4 or higher to run this program.</strong></p> -<p>To install an old <strong>and unsupported</strong> version of npm that works on node v0.12 +<p><strong>You need node v6 or higher to run this program.</strong></p> +<p>To install an old <strong>and unsupported</strong> version of npm that works on node v5 and prior, clone the git repo and dig through the old tags and branches.</p> <p><strong>npm is configured to use npm, Inc.'s public package registry at <a href="https://registry.npmjs.org">https://registry.npmjs.org</a> by default.</strong></p> @@ -127,5 +127,5 @@ 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.6.0</p> +<p id="footer"><a href="../doc/README.html">README</a> — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-access.html b/deps/npm/html/doc/cli/npm-access.html index 5fb7cfb002..bbc9b1814b 100644 --- a/deps/npm/html/doc/cli/npm-access.html +++ b/deps/npm/html/doc/cli/npm-access.html @@ -86,5 +86,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.6.0</p> +<p id="footer">npm-access — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-adduser.html b/deps/npm/html/doc/cli/npm-adduser.html index 90d247f5f5..629130d14f 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.6.0</p> +<p id="footer">npm-adduser — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-audit.html b/deps/npm/html/doc/cli/npm-audit.html new file mode 100644 index 0000000000..e7e9c74b02 --- /dev/null +++ b/deps/npm/html/doc/cli/npm-audit.html @@ -0,0 +1,88 @@ +<!doctype html> +<html> + <title>npm-audit</title> + <meta charset="utf-8"> + <link rel="stylesheet" type="text/css" href="../../static/style.css"> + <link rel="canonical" href="https://www.npmjs.org/doc/cli/npm-audit.html"> + <script async=true src="../../static/toc.js"></script> + + <body> + <div id="wrapper"> + +<h1><a href="../cli/npm-audit.html">npm-audit</a></h1> <p>Run a security audit</p> +<h2 id="synopsis">SYNOPSIS</h2> +<pre><code>npm audit [--json] +npm audit fix [--force|--package-lock-only|--dry-run|--production|--only=dev] +</code></pre><h2 id="examples">EXAMPLES</h2> +<p>Scan your project for vulnerabilities and automatically install any compatible +updates to vulnerable dependencies:</p> +<pre><code>$ npm audit fix +</code></pre><p>Run <code>audit fix</code> without modifying <code>node_modules</code>, but still updating the +pkglock:</p> +<pre><code>$ npm audit fix --package-lock-only +</code></pre><p>Skip updating <code>devDependencies</code>:</p> +<pre><code>$ npm audit fix --only=prod +</code></pre><p>Have <code>audit fix</code> install semver-major updates to toplevel dependencies, not just +semver-compatible ones:</p> +<pre><code>$ npm audit fix --force +</code></pre><p>Do a dry run to get an idea of what <code>audit fix</code> will do, and <em>also</em> output +install information in JSON format:</p> +<pre><code>$ npm audit fix --dry-run --json +</code></pre><p>Scan your project for vulnerabilities and just show the details, without fixing +anything:</p> +<pre><code>$ npm audit +</code></pre><p>Get the detailed audit report in JSON format:</p> +<pre><code>$ npm audit --json +</code></pre><h2 id="description">DESCRIPTION</h2> +<p>The audit command submits a description of the dependencies configured in +your project to your default registry and asks for a report of known +vulnerabilities. The report returned includes instructions on how to act on +this information.</p> +<p>You can also have npm automatically fix the vulnerabilities by running <code>npm +audit fix</code>. Note that some vulnerabilities cannot be fixed automatically and +will require manual intervention or review. Also note that since <code>npm audit fix</code> +runs a full-fledged <code>npm install</code> under the hood, all configs that apply to the +installer will also apply to <code>npm install</code> -- so things like <code>npm audit fix +--package-lock-only</code> will work as expected.</p> +<h2 id="content-submitted">CONTENT SUBMITTED</h2> +<ul> +<li>npm_version</li> +<li>node_version</li> +<li>platform</li> +<li>node_env</li> +<li>A scrubbed version of your package-lock.json or npm-shrinkwrap.json</li> +</ul> +<h3 id="scrubbing">SCRUBBING</h3> +<p>In order to ensure that potentially sensitive information is not included in +the audit data bundle, some dependencies may have their names (and sometimes +versions) replaced with opaque non-reversible identifiers. It is done for +the following dependency types:</p> +<ul> +<li>Any module referencing a scope that is configured for a non-default +registry has its name scrubbed. (That is, a scope you did a <code>npm login --scope=@ourscope</code> for.)</li> +<li>All git dependencies have their names and specifiers scrubbed.</li> +<li>All remote tarball dependencies have their names and specifiers scrubbed.</li> +<li>All local directory and tarball dependencies have their names and specifiers scrubbed.</li> +</ul> +<p>The non-reversible identifiers are a sha256 of a session-specific UUID and the +value being replaced, ensuring a consistent value within the payload that is +different between runs.</p> +<h2 id="see-also">SEE ALSO</h2> +<ul> +<li><a href="../cli/npm-install.html">npm-install(1)</a></li> +<li><a href="../files/package-locks.html">package-locks(5)</a></li> +<li><a href="../misc/config.html">config(7)</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-audit — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-bin.html b/deps/npm/html/doc/cli/npm-bin.html index 677f621a97..75cd0fef71 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.6.0</p> +<p id="footer">npm-bin — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-bugs.html b/deps/npm/html/doc/cli/npm-bugs.html index 3437dd4380..c5d564941a 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.6.0</p> +<p id="footer">npm-bugs — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-build.html b/deps/npm/html/doc/cli/npm-build.html index 51544a4532..ffdbfed446 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.6.0</p> +<p id="footer">npm-build — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-bundle.html b/deps/npm/html/doc/cli/npm-bundle.html index 94cf6ed12b..cc6494ba6f 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.6.0</p> +<p id="footer">npm-bundle — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-cache.html b/deps/npm/html/doc/cli/npm-cache.html index 71d5297a9c..8f3b4d2b1e 100644 --- a/deps/npm/html/doc/cli/npm-cache.html +++ b/deps/npm/html/doc/cli/npm-cache.html @@ -89,5 +89,5 @@ verify</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-cache — npm@5.6.0</p> +<p id="footer">npm-cache — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-ci.html b/deps/npm/html/doc/cli/npm-ci.html new file mode 100644 index 0000000000..82791325f1 --- /dev/null +++ b/deps/npm/html/doc/cli/npm-ci.html @@ -0,0 +1,64 @@ +<!doctype html> +<html> + <title>npm-ci</title> + <meta charset="utf-8"> + <link rel="stylesheet" type="text/css" href="../../static/style.css"> + <link rel="canonical" href="https://www.npmjs.org/doc/cli/npm-ci.html"> + <script async=true src="../../static/toc.js"></script> + + <body> + <div id="wrapper"> + +<h1><a href="../cli/npm-ci.html">npm-ci</a></h1> <p>Install a project with a clean slate</p> +<h2 id="synopsis">SYNOPSIS</h2> +<pre><code>npm ci +</code></pre><h2 id="example">EXAMPLE</h2> +<p>Make sure you have a package-lock and an up-to-date install:</p> +<pre><code>$ cd ./my/npm/project +$ npm install +added 154 packages in 10s +$ ls | grep package-lock +</code></pre><p>Run <code>npm ci</code> in that project</p> +<pre><code>$ npm ci +added 154 packages in 5s +</code></pre><p>Configure Travis to build using <code>npm ci</code> instead of <code>npm install</code>:</p> +<pre><code># .travis.yml +install: +- npm ci +# keep the npm cache around to speed up installs +cache: + directories: + - "$HOME/.npm" +</code></pre><h2 id="description">DESCRIPTION</h2> +<p>This command is similar to <code><a href="../cli/npm-install.html">npm-install(1)</a></code>, except it's meant to be used in +automated environments such as test platforms, continuous integration, and +deployment. It can be significantly faster than a regular npm install by +skipping certain user-oriented features. It is also more strict than a regular +install, which can help catch errors or inconsistencies caused by the +incrementally-installed local environments of most npm users.</p> +<p>In short, the main differences between using <code>npm install</code> and <code>npm ci</code> are:</p> +<ul> +<li>The project <strong>must</strong> have an existing <code>package-lock.json</code> or <code>npm-shrinkwrap.json</code>.</li> +<li>If dependencies in the package lock do not match those in <code>package.json</code>, <code>npm ci</code> will exit with an error, instead of updating the package lock.</li> +<li><code>npm ci</code> can only install entire projects at a time: individual dependencies cannot be added with this command.</li> +<li>If a <code>node_modules</code> is already present, it will be automatically removed before <code>npm ci</code> begins its install.</li> +<li>It will never write to <code>package.json</code> or any of the package-locks: installs are essentially frozen.</li> +</ul> +<h2 id="see-also">SEE ALSO</h2> +<ul> +<li><a href="../cli/npm-install.html">npm-install(1)</a></li> +<li><a href="../files/npm-package-locks.html">npm-package-locks(5)</a></li> +</ul> + +</div> + +<table border=0 cellspacing=0 cellpadding=0 id=npmlogo> +<tr><td style="width:180px;height:10px;background:rgb(237,127,127)" colspan=18> </td></tr> +<tr><td rowspan=4 style="width:10px;height:10px;background:rgb(237,127,127)"> </td><td style="width:40px;height:10px;background:#fff" colspan=4> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=4> </td><td style="width:40px;height:10px;background:#fff" colspan=4> </td><td rowspan=4 style="width:10px;height:10px;background:rgb(237,127,127)"> </td><td colspan=6 style="width:60px;height:10px;background:#fff"> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=4> </td></tr> +<tr><td colspan=2 style="width:20px;height:30px;background:#fff" rowspan=3> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:20px;height:10px;background:#fff" rowspan=4 colspan=2> </td><td style="width:10px;height:20px;background:rgb(237,127,127)" rowspan=2> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:20px;height:10px;background:#fff" rowspan=3 colspan=2> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td></tr> +<tr><td style="width:10px;height:10px;background:#fff" rowspan=2> </td></tr> +<tr><td style="width:10px;height:10px;background:#fff"> </td></tr> +<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> +<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> +</table> +<p id="footer">npm-ci — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-completion.html b/deps/npm/html/doc/cli/npm-completion.html index 7a37048a8a..381ce6ba8f 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.6.0</p> +<p id="footer">npm-completion — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-config.html b/deps/npm/html/doc/cli/npm-config.html index ccacfe9c39..dad4fb527f 100644 --- a/deps/npm/html/doc/cli/npm-config.html +++ b/deps/npm/html/doc/cli/npm-config.html @@ -68,5 +68,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.6.0</p> +<p id="footer">npm-config — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-dedupe.html b/deps/npm/html/doc/cli/npm-dedupe.html index e21605193f..6e78044137 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.6.0</p> +<p id="footer">npm-dedupe — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-deprecate.html b/deps/npm/html/doc/cli/npm-deprecate.html index f82a6b6d18..7f6af91be8 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.6.0</p> +<p id="footer">npm-deprecate — npm@6.1.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 6f8bc9744f..0a2b2861dc 100644 --- a/deps/npm/html/doc/cli/npm-dist-tag.html +++ b/deps/npm/html/doc/cli/npm-dist-tag.html @@ -88,5 +88,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.6.0</p> +<p id="footer">npm-dist-tag — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-docs.html b/deps/npm/html/doc/cli/npm-docs.html index 165159af15..43763b2cc2 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.6.0</p> +<p id="footer">npm-docs — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-doctor.html b/deps/npm/html/doc/cli/npm-doctor.html index 8eba9f172d..5d3dff5245 100644 --- a/deps/npm/html/doc/cli/npm-doctor.html +++ b/deps/npm/html/doc/cli/npm-doctor.html @@ -32,7 +32,7 @@ old versions of npm. Since npm is constantly improving, running <code>npm@latest better than an old version.</p> <p><code>npm doctor</code> verifies the following items in your environment, and if there are any recommended changes, it will display them.</p> -<h3 id="-npm-ping-"><code>npm ping</code></h3> +<h3 id="npm-ping"><code>npm ping</code></h3> <p>By default, npm installs from the primary npm registry, <code>registry.npmjs.org</code>. <code>npm doctor</code> hits a special ping endpoint within the registry. This can also be checked with <code>npm ping</code>. If this check fails, you may be using a proxy that @@ -42,7 +42,7 @@ HTTPS to <code>registry.npmjs.org</code>.</p> what that is by running <code>npm config get registry</code>), and if you're using a private registry that doesn't support the <code>/whoami</code> endpoint supported by the primary registry, this check may fail.</p> -<h3 id="-npm-v-"><code>npm -v</code></h3> +<h3 id="npm-v"><code>npm -v</code></h3> <p>While Node.js may come bundled with a particular version of npm, it's the policy of the CLI team that we recommend all users run <code>npm@latest</code> if they can. As the CLI is maintained by a small team of contributors, there are only @@ -50,21 +50,21 @@ resources for a single line of development, so npm's own long-term support releases typically only receive critical security and regression fixes. The team believes that the latest tested version of npm is almost always likely to be the most functional and defect-free version of npm.</p> -<h3 id="-node-v-"><code>node -v</code></h3> +<h3 id="node-v"><code>node -v</code></h3> <p>For most users, in most circumstances, the best version of Node will be the latest long-term support (LTS) release. Those of you who want access to new ECMAscript features or bleeding-edge changes to Node's standard library may be running a newer version, and some of you may be required to run an older version of Node because of enterprise change control policies. That's OK! But in general, the npm team recommends that most users run Node.js LTS.</p> -<h3 id="-npm-config-get-registry-"><code>npm config get registry</code></h3> +<h3 id="npm-config-get-registry"><code>npm config get registry</code></h3> <p>Some of you may be installing from private package registries for your project or company. That's great! Others of you may be following tutorials or StackOverflow questions in an effort to troubleshoot problems you may be having. Sometimes, this may entail changing the registry you're pointing at. This part of <code>npm doctor</code> just lets you, and maybe whoever's helping you with support, know that you're not using the default registry.</p> -<h3 id="-which-git-"><code>which git</code></h3> +<h3 id="which-git"><code>which git</code></h3> <p>While it's documented in the <a href="../../doc/README.html">README</a>, it may not be obvious that npm needs Git installed to do many of the things that it does. Also, in some cases – especially on Windows – you may have Git set up in such a way that it's not @@ -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.6.0</p> +<p id="footer">npm-doctor — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-edit.html b/deps/npm/html/doc/cli/npm-edit.html index 651990084d..3d0b4a1bdc 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.6.0</p> +<p id="footer">npm-edit — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-explore.html b/deps/npm/html/doc/cli/npm-explore.html index bab3a861ec..4d5628ddbf 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.6.0</p> +<p id="footer">npm-explore — npm@6.1.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 01b1ff62d2..06204f99c4 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.6.0</p> +<p id="footer">npm-help-search — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-help.html b/deps/npm/html/doc/cli/npm-help.html index 8adf3b3843..9301975467 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.6.0</p> +<p id="footer">npm-help — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-hook.html b/deps/npm/html/doc/cli/npm-hook.html new file mode 100644 index 0000000000..b4e513f2fc --- /dev/null +++ b/deps/npm/html/doc/cli/npm-hook.html @@ -0,0 +1,63 @@ +<!doctype html> +<html> + <title>npm-hook</title> + <meta charset="utf-8"> + <link rel="stylesheet" type="text/css" href="../../static/style.css"> + <link rel="canonical" href="https://www.npmjs.org/doc/cli/npm-hook.html"> + <script async=true src="../../static/toc.js"></script> + + <body> + <div id="wrapper"> + +<h1><a href="../cli/npm-hook.html">npm-hook</a></h1> <p>Manage registry hooks</p> +<h2 id="synopsis">SYNOPSIS</h2> +<pre><code>npm hook ls [pkg] +npm hook add <entity> <url> <secret> +npm hook update <id> <url> [secret] +npm hook rm <id> +</code></pre><h2 id="example">EXAMPLE</h2> +<p>Add a hook to watch a package for changes:</p> +<pre><code>$ npm hook add lodash https://example.com/ my-shared-secret +</code></pre><p>Add a hook to watch packages belonging to the user <code>substack</code>:</p> +<pre><code>$ npm hook add ~substack https://example.com/ my-shared-secret +</code></pre><p>Add a hook to watch packages in the scope <code>@npm</code></p> +<pre><code>$ npm hook add @npm https://example.com/ my-shared-secret +</code></pre><p>List all your active hooks:</p> +<pre><code>$ npm hook ls +</code></pre><p>List your active hooks for the <code>lodash</code> package:</p> +<pre><code>$ npm hook ls lodash +</code></pre><p>Update an existing hook's url:</p> +<pre><code>$ npm hook update id-deadbeef https://my-new-website.here/ +</code></pre><p>Remove a hook:</p> +<pre><code>$ npm hook rm id-deadbeef +</code></pre><h2 id="description">DESCRIPTION</h2> +<p>Allows you to manage <a href="http://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm">npm +hooks</a>, +including adding, removing, listing, and updating.</p> +<p>Hooks allow you to configure URL endpoints that will be notified whenever a +change happens to any of the supported entity types. Three different types of +entities can be watched by hooks: packages, owners, and scopes.</p> +<p>To create a package hook, simply reference the package name.</p> +<p>To create an owner hook, prefix the owner name with <code>~</code> (as in, <code>~youruser</code>).</p> +<p>To create a scope hook, prefix the scope name with <code>@</code> (as in, <code>@yourscope</code>).</p> +<p>The hook <code>id</code> used by <code>update</code> and <code>rm</code> are the IDs listed in <code>npm hook ls</code> for +that particular hook.</p> +<p>The shared secret will be sent along to the URL endpoint so you can verify the +request came from your own configured hook.</p> +<h2 id="see-also">SEE ALSO</h2> +<ul> +<li><a href="http://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm">"Introducing Hooks" blog post</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-hook — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-init.html b/deps/npm/html/doc/cli/npm-init.html index 115c9b2185..4e405c2ccf 100644 --- a/deps/npm/html/doc/cli/npm-init.html +++ b/deps/npm/html/doc/cli/npm-init.html @@ -9,26 +9,44 @@ <body> <div id="wrapper"> -<h1><a href="../cli/npm-init.html">npm-init</a></h1> <p>Interactively create a package.json file</p> +<h1><a href="../cli/npm-init.html">npm-init</a></h1> <p>create a package.json file</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm init [-f|--force|-y|--yes] +<pre><code>npm init [--force|-f|--yes|-y|--scope] +npm init <@scope> (same as `npx <@scope>/create`) +npm init [<@scope>/]<name> (same as `npx [<@scope>/]create-<name>`) +</code></pre><h2 id="examples">EXAMPLES</h2> +<p>Create a new React-based project using <a href="https://npm.im/create-react-app"><code>create-react-app</code></a>:</p> +<pre><code>$ npm init react-app ./my-react-app +</code></pre><p>Create a new <code>esm</code>-compatible package using <a href="https://npm.im/create-esm"><code>create-esm</code></a>:</p> +<pre><code>$ mkdir my-esm-lib && cd my-esm-lib +$ npm init esm --yes +</code></pre><p>Generate a plain old package.json using legacy init:</p> +<pre><code>$ mkdir my-npm-pkg && cd my-npm-pkg +$ git init +$ npm init +</code></pre><p>Generate it without having it ask any questions:</p> +<pre><code>$ npm init -y </code></pre><h2 id="description">DESCRIPTION</h2> -<p>This will ask you a bunch of questions, and then write a package.json for you.</p> -<p>It attempts to make reasonable guesses about what you want things to be set to, -and then writes a package.json file with the options you've selected.</p> -<p>If you already have a package.json file, it'll read that first, and default to -the options in there.</p> -<p>It is strictly additive, so it does not delete options from your package.json -without a really good reason to do so.</p> -<p>If you invoke it with <code>-f</code>, <code>--force</code>, <code>-y</code>, or <code>--yes</code>, it will use only -defaults and not prompt you for any options.</p> -<h2 id="configuration">CONFIGURATION</h2> -<h3 id="scope">scope</h3> +<p><code>npm init <initializer></code> can be used to set up a new or existing npm package.</p> +<p><code>initializer</code> in this case is an npm package named <code>create-<initializer></code>, which +will be installed by <a href="https://npm.im/npx"><code><a href="../cli/npx.html">npx(1)</a></code></a>, and then have its main bin +executed -- presumably creating or updating <code>package.json</code> and running any other +initialization-related operations.</p> +<p>The init command is transformed to a corresponding <code>npx</code> operation as follows:</p> <ul> -<li>Default: none</li> -<li>Type: String</li> +<li><code>npm init foo</code> -> <code>npx create-foo</code></li> +<li><code>npm init @usr/foo</code> -> <code>npx @usr/create-foo</code></li> +<li><code>npm init @usr</code> -> <code>npx @usr/create</code></li> </ul> -<p>The scope under which the new module should be created.</p> +<p>Any additional options will be passed directly to the command, so <code>npm init foo +--hello</code> will map to <code>npx create-foo --hello</code>.</p> +<p>If the initializer is omitted (by just calling <code>npm init</code>), init will fall back +to legacy init behavior. It will ask you a bunch of questions, and then write a +package.json for you. It will attempt to make reasonable guesses based on +existing fields, dependencies, and options selected. It is strictly additive, so +it will keep any fields and values that were already set. You can also use +<code>-y</code>/<code>--yes</code> to skip the questionnaire altogether. If you pass <code>--scope</code>, it +will create a scoped package.</p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="https://github.com/isaacs/init-package-json">https://github.com/isaacs/init-package-json</a></li> @@ -48,5 +66,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.6.0</p> +<p id="footer">npm-init — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-install-ci-test.html b/deps/npm/html/doc/cli/npm-install-ci-test.html new file mode 100644 index 0000000000..537a0263bf --- /dev/null +++ b/deps/npm/html/doc/cli/npm-install-ci-test.html @@ -0,0 +1,36 @@ +<!doctype html> +<html> + <title>npm-install-ci-test</title> + <meta charset="utf-8"> + <link rel="stylesheet" type="text/css" href="../../static/style.css"> + <link rel="canonical" href="https://www.npmjs.org/doc/cli/npm-install-ci-test.html"> + <script async=true src="../../static/toc.js"></script> + + <body> + <div id="wrapper"> + +<h1>npm <a href="../cli/install-ci-test.html">install-ci-test</a></h1> <p>Install a project with a clean slate and run tests</p> +<h2 id="synopsis">SYNOPSIS</h2> +<pre><code>npm install-ci-test + +alias: npm cit +</code></pre><h2 id="description">DESCRIPTION</h2> +<p>This command runs an <code>npm ci</code> followed immediately by an <code>npm test</code>.</p> +<h2 id="see-also">SEE ALSO</h2> +<ul> +<li><a href="../cli/npm-ci.html">npm-ci(1)</a></li> +<li><a href="../cli/npm-test.html">npm-test(1)</a></li> +</ul> + +</div> + +<table border=0 cellspacing=0 cellpadding=0 id=npmlogo> +<tr><td style="width:180px;height:10px;background:rgb(237,127,127)" colspan=18> </td></tr> +<tr><td rowspan=4 style="width:10px;height:10px;background:rgb(237,127,127)"> </td><td style="width:40px;height:10px;background:#fff" colspan=4> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=4> </td><td style="width:40px;height:10px;background:#fff" colspan=4> </td><td rowspan=4 style="width:10px;height:10px;background:rgb(237,127,127)"> </td><td colspan=6 style="width:60px;height:10px;background:#fff"> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=4> </td></tr> +<tr><td colspan=2 style="width:20px;height:30px;background:#fff" rowspan=3> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:20px;height:10px;background:#fff" rowspan=4 colspan=2> </td><td style="width:10px;height:20px;background:rgb(237,127,127)" rowspan=2> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:20px;height:10px;background:#fff" rowspan=3 colspan=2> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td></tr> +<tr><td style="width:10px;height:10px;background:#fff" rowspan=2> </td></tr> +<tr><td style="width:10px;height:10px;background:#fff"> </td></tr> +<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> +<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> +</table> +<p id="footer">npm-install-ci-test — npm@6.1.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 71262400b3..beb2d312a9 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.6.0</p> +<p id="footer">npm-install-test — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-install.html b/deps/npm/html/doc/cli/npm-install.html index 5989cc25a1..5bc9cd985b 100644 --- a/deps/npm/html/doc/cli/npm-install.html +++ b/deps/npm/html/doc/cli/npm-install.html @@ -54,6 +54,10 @@ after packing it up into a tarball (b).</p> <p> With the <code>--production</code> flag (or when the <code>NODE_ENV</code> environment variable is set to <code>production</code>), npm will not install modules listed in <code>devDependencies</code>.</p> +<blockquote> +<p>NOTE: The <code>--production</code> flag has no particular meaning when adding a + dependency to a project.</p> +</blockquote> </li> <li><p><code>npm install <folder></code>:</p> <p> Install the package in the directory as a symlink in the current project. @@ -281,11 +285,14 @@ being installed.</p> <p>The <code>--no-shrinkwrap</code> argument, which will ignore an available package lock or shrinkwrap file and use the package.json instead.</p> <p>The <code>--no-package-lock</code> argument will prevent npm from creating a -<code>package-lock.json</code> file.</p> +<code>package-lock.json</code> file. When running with package-lock's disabled npm +will not automatically prune your node modules when installing.</p> <p>The <code>--nodedir=/path/to/node/source</code> argument will allow npm to find the node source code so that npm can compile native modules.</p> <p>The <code>--only={prod[uction]|dev[elopment]}</code> argument will cause either only <code>devDependencies</code> or only non-<code>devDependencies</code> to be installed regardless of the <code>NODE_ENV</code>.</p> +<p>The <code>--no-audit</code> argument can be used to disable sending of audit reports to +the configured registries. See <code><a href="../cli/npm-audit.html">npm-audit(1)</a></code> for details on what is sent.</p> <p>See <code><a href="../misc/npm-config.html">npm-config(7)</a></code>. Many of the configuration params have some effect on installation, since that's most of what npm does.</p> <h2 id="algorithm">ALGORITHM</h2> @@ -344,6 +351,7 @@ affects a real use-case, it will be investigated.</p> <ul> <li><a href="../files/npm-folders.html">npm-folders(5)</a></li> <li><a href="../cli/npm-update.html">npm-update(1)</a></li> +<li><a href="../cli/npm-audit.html">npm-audit(1)</a></li> <li><a href="../cli/npm-link.html">npm-link(1)</a></li> <li><a href="../cli/npm-rebuild.html">npm-rebuild(1)</a></li> <li><a href="../misc/npm-scripts.html">npm-scripts(7)</a></li> @@ -369,5 +377,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.6.0</p> +<p id="footer">npm-install — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-link.html b/deps/npm/html/doc/cli/npm-link.html index 57a6ae8673..b84aad751d 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.6.0</p> +<p id="footer">npm-link — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-logout.html b/deps/npm/html/doc/cli/npm-logout.html index a06341b2d2..3929410fa1 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.6.0</p> +<p id="footer">npm-logout — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-ls.html b/deps/npm/html/doc/cli/npm-ls.html index 4ba0917179..cfbe4ee303 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.6.0 /path/to/npm +<pre><code>npm@6.1.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> @@ -68,7 +68,7 @@ project.</p> <li>Default: false</li> </ul> <p>Display only the dependency tree for packages in <code>dependencies</code>.</p> -<h3 id="dev">dev</h3> +<h3 id="dev-development">dev / development</h3> <ul> <li>Type: Boolean</li> <li>Default: false</li> @@ -110,5 +110,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.6.0</p> +<p id="footer">npm-ls — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-outdated.html b/deps/npm/html/doc/cli/npm-outdated.html index d59e0548a3..319f1ae45f 100644 --- a/deps/npm/html/doc/cli/npm-outdated.html +++ b/deps/npm/html/doc/cli/npm-outdated.html @@ -32,6 +32,8 @@ always be seeing only top-level dependencies that are outdated.</li> <li><code>package type</code> (when using <code>--long</code> / <code>-l</code>) tells you whether this package is a <code>dependency</code> or a <code>devDependency</code>. Packages not included in <code>package.json</code> are always marked <code>dependencies</code>.</li> +<li>Red means there's a newer version matching your semver requirements, so you should update now.</li> +<li>Yellow indicates that there's a newer version above your semver requirements (usually new major, or new 0.x minor) so proceed with caution.</li> </ul> <h3 id="an-example">An example</h3> <pre><code>$ npm outdated @@ -58,10 +60,9 @@ The installed committish might satisfy the dependency specifier (if it's something immutable, like a commit SHA), or it might not, so <code>npm outdated</code> and <code>npm update</code> have to fetch Git repos to check. This is why currently doing a reinstall of a Git dependency always forces a new clone and install.</li> -<li><code>npm@3.5.2</code> is marked as "wanted", but "latest" is <code>npm@3.5.1</code> because npm -uses dist-tags to manage its <code>latest</code> and <code>next</code> release channels. <code>npm update</code> -will install the <em>newest</em> version, but <code>npm install npm</code> (with no semver range) -will install whatever's tagged as <code>latest</code>.</li> +<li><a href="mailto:`npm@3.5.2">`npm@3.5.2</a><code>is marked as "wanted", but "latest" is</code><a href="mailto:npm@3.5.1">npm@3.5.1</a><code>because npm +uses dist-tags to manage its</code>latest<code>and</code>next<code>release channels.</code>npm update<code>will install the _newest_ version, but</code>npm install npm<code>(with no semver range) +will install whatever's tagged as</code>latest`.</li> <li><code>once</code> is just plain out of date. Reinstalling <code>node_modules</code> from scratch or running <code>npm update</code> will bring it up to spec.</li> </ul> @@ -116,5 +117,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.6.0</p> +<p id="footer">npm-outdated — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-owner.html b/deps/npm/html/doc/cli/npm-owner.html index 6b28ab48d1..1c1ce66534 100644 --- a/deps/npm/html/doc/cli/npm-owner.html +++ b/deps/npm/html/doc/cli/npm-owner.html @@ -54,5 +54,5 @@ with <code>--otp</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-owner — npm@5.6.0</p> +<p id="footer">npm-owner — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-pack.html b/deps/npm/html/doc/cli/npm-pack.html index 35e6670bef..d3a560f14c 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.6.0</p> +<p id="footer">npm-pack — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-ping.html b/deps/npm/html/doc/cli/npm-ping.html index 4b67c2686e..0e0d2afc7e 100644 --- a/deps/npm/html/doc/cli/npm-ping.html +++ b/deps/npm/html/doc/cli/npm-ping.html @@ -36,5 +36,5 @@ If it works it will output something like:</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-ping — npm@5.6.0</p> +<p id="footer">npm-ping — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-prefix.html b/deps/npm/html/doc/cli/npm-prefix.html index ebb2f6a3c6..d9cdfd9782 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.6.0</p> +<p id="footer">npm-prefix — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-profile.html b/deps/npm/html/doc/cli/npm-profile.html index 3d952205f4..60fece551e 100644 --- a/deps/npm/html/doc/cli/npm-profile.html +++ b/deps/npm/html/doc/cli/npm-profile.html @@ -90,4 +90,4 @@ available on non npmjs.com registries.</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-profile — npm@5.6.0</p> +<p id="footer">npm-profile — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-prune.html b/deps/npm/html/doc/cli/npm-prune.html index f71aa0c212..1c3ce7eb02 100644 --- a/deps/npm/html/doc/cli/npm-prune.html +++ b/deps/npm/html/doc/cli/npm-prune.html @@ -11,7 +11,7 @@ <h1><a href="../cli/npm-prune.html">npm-prune</a></h1> <p>Remove extraneous packages</p> <h2 id="synopsis">SYNOPSIS</h2> -<pre><code>npm prune [[<@scope>/]<pkg>...] [--production] +<pre><code>npm prune [[<@scope>/]<pkg>...] [--production] [--dry-run] [--json] </code></pre><h2 id="description">DESCRIPTION</h2> <p>This command removes "extraneous" packages. If a package name is provided, then only packages matching one of the supplied names are @@ -20,8 +20,16 @@ removed.</p> package's dependencies list.</p> <p>If the <code>--production</code> flag is specified or the <code>NODE_ENV</code> environment variable is set to <code>production</code>, this command will remove the packages -specified in your <code>devDependencies</code>. Setting <code>--production=false</code> will +specified in your <code>devDependencies</code>. Setting <code>--no-production</code> will negate <code>NODE_ENV</code> being set to <code>production</code>.</p> +<p>If the <code>--dry-run</code> flag is used then no changes will actually be made.</p> +<p>If the <code>--json</code> flag is used then the changes <code>npm prune</code> made (or would +have made with <code>--dry-run</code>) are printed as a JSON object.</p> +<p>In normal operation with package-locks enabled, extraneous modules are +pruned automatically when modules are installed and you'll only need +this command with the <code>--production</code> flag.</p> +<p>If you've disabled package-locks then extraneous modules will not be removed +and it's up to you to run <code>npm prune</code> from time-to-time to remove them.</p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../cli/npm-uninstall.html">npm-uninstall(1)</a></li> @@ -40,5 +48,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.6.0</p> +<p id="footer">npm-prune — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-publish.html b/deps/npm/html/doc/cli/npm-publish.html index c8a0b691e1..5a3c8b8f16 100644 --- a/deps/npm/html/doc/cli/npm-publish.html +++ b/deps/npm/html/doc/cli/npm-publish.html @@ -85,5 +85,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.6.0</p> +<p id="footer">npm-publish — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-rebuild.html b/deps/npm/html/doc/cli/npm-rebuild.html index 136192342a..4361ac43c1 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.6.0</p> +<p id="footer">npm-rebuild — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-repo.html b/deps/npm/html/doc/cli/npm-repo.html index 12e6b1748e..e11513ceb0 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.6.0</p> +<p id="footer">npm-repo — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-restart.html b/deps/npm/html/doc/cli/npm-restart.html index 4f9aacecf1..918d331de4 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.6.0</p> +<p id="footer">npm-restart — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-root.html b/deps/npm/html/doc/cli/npm-root.html index a4e9aa9bd6..c97d05bdcd 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.6.0</p> +<p id="footer">npm-root — npm@6.1.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 489fbccb09..c3ed88b8f1 100644 --- a/deps/npm/html/doc/cli/npm-run-script.html +++ b/deps/npm/html/doc/cli/npm-run-script.html @@ -59,6 +59,9 @@ not found in the <code>PATH</code>.</p> <p>If you try to run a script without having a <code>node_modules</code> directory and it fails, you will be given a warning to run <code>npm install</code>, just in case you've forgotten.</p> <p>You can use the <code>--silent</code> flag to prevent showing <code>npm ERR!</code> output on error.</p> +<p>You can use the <code>--if-present</code> flag to avoid exiting with a non-zero exit code +when the script is undefined. This lets you run potentially undefined scripts +without breaking the execution chain.</p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../misc/npm-scripts.html">npm-scripts(7)</a></li> @@ -80,5 +83,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.6.0</p> +<p id="footer">npm-run-script — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-search.html b/deps/npm/html/doc/cli/npm-search.html index df759928a7..30a47caf7d 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.6.0</p> +<p id="footer">npm-search — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-shrinkwrap.html b/deps/npm/html/doc/cli/npm-shrinkwrap.html index 629f5b69a7..b4a740e413 100644 --- a/deps/npm/html/doc/cli/npm-shrinkwrap.html +++ b/deps/npm/html/doc/cli/npm-shrinkwrap.html @@ -41,5 +41,5 @@ of package locks in npm, see <a href="../files/npm-package-locks.html">npm-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-shrinkwrap — npm@5.6.0</p> +<p id="footer">npm-shrinkwrap — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-star.html b/deps/npm/html/doc/cli/npm-star.html index a957ff479f..ef57f2254c 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.6.0</p> +<p id="footer">npm-star — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-stars.html b/deps/npm/html/doc/cli/npm-stars.html index ff6dbfb314..9b28be20e0 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.6.0</p> +<p id="footer">npm-stars — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-start.html b/deps/npm/html/doc/cli/npm-start.html index 0c0dfb3ae1..258673ccfd 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.6.0</p> +<p id="footer">npm-start — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-stop.html b/deps/npm/html/doc/cli/npm-stop.html index 9c04332e68..88ce21fd9d 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.6.0</p> +<p id="footer">npm-stop — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-team.html b/deps/npm/html/doc/cli/npm-team.html index 81d74fa0a7..9c89f72947 100644 --- a/deps/npm/html/doc/cli/npm-team.html +++ b/deps/npm/html/doc/cli/npm-team.html @@ -39,6 +39,9 @@ If performed on an organization name, will return a list of existing teams under that organization. If performed on a team, it will instead return a list of all users belonging to that particular team.</p> </li> +<li><p>edit: +Edit a current team.</p> +</li> </ul> <h2 id="details">DETAILS</h2> <p><code>npm team</code> always operates directly on the current registry, configurable from @@ -67,5 +70,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.6.0</p> +<p id="footer">npm-team — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-test.html b/deps/npm/html/doc/cli/npm-test.html index 280e69f3a1..4abe456952 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.6.0</p> +<p id="footer">npm-test — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-token.html b/deps/npm/html/doc/cli/npm-token.html index 8ec2f5fbec..c39e39779a 100644 --- a/deps/npm/html/doc/cli/npm-token.html +++ b/deps/npm/html/doc/cli/npm-token.html @@ -73,4 +73,4 @@ This will NOT accept the truncated token found in <code>npm token list</code> ou <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;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-token — npm@5.6.0</p> +<p id="footer">npm-token — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-uninstall.html b/deps/npm/html/doc/cli/npm-uninstall.html index dd430d0796..9a6b4ec1d7 100644 --- a/deps/npm/html/doc/cli/npm-uninstall.html +++ b/deps/npm/html/doc/cli/npm-uninstall.html @@ -63,5 +63,5 @@ npm uninstall lodash --no-save <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;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.6.0</p> +<p id="footer">npm-uninstall — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-unpublish.html b/deps/npm/html/doc/cli/npm-unpublish.html index 721de2828f..72e84ce862 100644 --- a/deps/npm/html/doc/cli/npm-unpublish.html +++ b/deps/npm/html/doc/cli/npm-unpublish.html @@ -29,7 +29,7 @@ package again, a new version number must be used.</p> <p>With the default registry (<code>registry.npmjs.org</code>), unpublish is only allowed with versions published in the last 24 hours. If you are trying to unpublish a version published longer ago than that, -contact support@npmjs.com.</p> +contact <a href="mailto:support@npmjs.com">support@npmjs.com</a>.</p> <p>The scope is optional and follows the usual rules for <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code>.</p> <h2 id="see-also">SEE ALSO</h2> <ul> @@ -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.6.0</p> +<p id="footer">npm-unpublish — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-update.html b/deps/npm/html/doc/cli/npm-update.html index ddaf4104df..5b3f2a585d 100644 --- a/deps/npm/html/doc/cli/npm-update.html +++ b/deps/npm/html/doc/cli/npm-update.html @@ -24,12 +24,15 @@ as well.</p> packages.</p> <p>If no package name is specified, all packages in the specified location (global or local) will be updated.</p> -<p>As of <code>npm@2.6.1</code>, the <code>npm update</code> will only inspect top-level packages. -Prior versions of <code>npm</code> would also recursively inspect all dependencies. -To get the old behavior, use <code>npm --depth 9999 update</code>.</p> +<p>As of <a href="mailto:`npm@2.6.1">`npm@2.6.1</a><code>, the</code>npm update<code>will only inspect top-level packages. +Prior versions of</code>npm<code>would also recursively inspect all dependencies. +To get the old behavior, use</code>npm --depth 9999 update`.</p> +<p>As of <a href="mailto:`npm@5.0.0">`npm@5.0.0</a><code>, the</code>npm update<code>will change</code>package.json<code>to save the +new version as the minimum required dependency. To get the old behavior, +use</code>npm update --no-save`.</p> <h2 id="examples">EXAMPLES</h2> -<p>IMPORTANT VERSION NOTE: these examples assume <code>npm@2.6.1</code> or later. For -older versions of <code>npm</code>, you must specify <code>--depth 0</code> to get the behavior +<p>IMPORTANT VERSION NOTE: these examples assume <a href="mailto:`npm@2.6.1">`npm@2.6.1</a><code>or later. For +older versions of</code>npm<code>, you must specify</code>--depth 0` to get the behavior described below.</p> <p>For the examples below, assume that the current package is <code>app</code> and it depends on dependencies, <code>dep1</code> (<code>dep2</code>, .. etc.). The published versions of <code>dep1</code> are:</p> @@ -52,45 +55,28 @@ on dependencies, <code>dep1</code> (<code>dep2</code>, .. etc.). The published <pre><code>"dependencies": { "dep1": "^1.1.1" } -</code></pre><p>Then <code>npm update</code> will install <code>dep1@1.2.2</code>, because <code>1.2.2</code> is <code>latest</code> and -<code>1.2.2</code> satisfies <code>^1.1.1</code>.</p> +</code></pre><p>Then <code>npm update</code> will install <a href="mailto:`dep1@1.2.2">`dep1@1.2.2</a><code>, because</code>1.2.2<code>is</code>latest<code>and</code>1.2.2<code>satisfies</code>^1.1.1`.</p> <h3 id="tilde-dependencies">Tilde Dependencies</h3> <p>However, if <code>app</code>'s <code>package.json</code> contains:</p> <pre><code>"dependencies": { "dep1": "~1.1.1" } -</code></pre><p>In this case, running <code>npm update</code> will install <code>dep1@1.1.2</code>. Even though the <code>latest</code> -tag points to <code>1.2.2</code>, this version does not satisfy <code>~1.1.1</code>, which is equivalent -to <code>>=1.1.1 <1.2.0</code>. So the highest-sorting version that satisfies <code>~1.1.1</code> is used, -which is <code>1.1.2</code>.</p> +</code></pre><p>In this case, running <code>npm update</code> will install <a href="mailto:`dep1@1.1.2">`dep1@1.1.2</a><code>. Even though the</code>latest<code>tag points to</code>1.2.2<code>, this version does not satisfy</code>~1.1.1<code>, which is equivalent +to</code>>=1.1.1 <1.2.0<code>. So the highest-sorting version that satisfies</code>~1.1.1<code>is used, +which is</code>1.1.2`.</p> <h3 id="caret-dependencies-below-1-0-0">Caret Dependencies below 1.0.0</h3> <p>Suppose <code>app</code> has a caret dependency on a version below <code>1.0.0</code>, for example:</p> <pre><code>"dependencies": { "dep1": "^0.2.0" } -</code></pre><p><code>npm update</code> will install <code>dep1@0.2.0</code>, because there are no other -versions which satisfy <code>^0.2.0</code>.</p> +</code></pre><p><code>npm update</code> will install <a href="mailto:`dep1@0.2.0">`dep1@0.2.0</a><code>, because there are no other +versions which satisfy</code>^0.2.0`.</p> <p>If the dependence were on <code>^0.4.0</code>:</p> <pre><code>"dependencies": { "dep1": "^0.4.0" } -</code></pre><p>Then <code>npm update</code> will install <code>dep1@0.4.1</code>, because that is the highest-sorting -version that satisfies <code>^0.4.0</code> (<code>>= 0.4.0 <0.5.0</code>)</p> -<h3 id="recording-updates-with-save-">Recording Updates with <code>--save</code></h3> -<p>When you want to update a package and save the new version as -the minimum required dependency in <code>package.json</code>, you can use -<code>npm update -S</code> or <code>npm update --save</code>. For example if -<code>package.json</code> contains:</p> -<pre><code>"dependencies": { - "dep1": "^1.1.1" -} -</code></pre><p>Then <code>npm update --save</code> will install <code>dep1@1.2.2</code> (i.e., <code>latest</code>), -and <code>package.json</code> will be modified:</p> -<pre><code>"dependencies": { - "dep1": "^1.2.2" -} -</code></pre><p>Note that <code>npm</code> will only write an updated version to <code>package.json</code> -if it installs a new package.</p> +</code></pre><p>Then <code>npm update</code> will install <a href="mailto:`dep1@0.4.1">`dep1@0.4.1</a><code>, because that is the highest-sorting +version that satisfies</code>^0.4.0<code>(</code>>= 0.4.0 <0.5.0`)</p> <h3 id="updating-globally-installed-packages">Updating Globally-Installed Packages</h3> <p><code>npm update -g</code> will apply the <code>update</code> action to each globally installed package that is <code>outdated</code> -- that is, has a version that is different from @@ -118,5 +104,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.6.0</p> +<p id="footer">npm-update — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-version.html b/deps/npm/html/doc/cli/npm-version.html index e8da71b67a..3349206a76 100644 --- a/deps/npm/html/doc/cli/npm-version.html +++ b/deps/npm/html/doc/cli/npm-version.html @@ -18,7 +18,7 @@ 'npm ls' to inspect current package/dependency versions </code></pre><h2 id="description">DESCRIPTION</h2> <p>Run this in a package directory to bump the version and write the new -data back to <code>package.json</code> and, if present, <code>npm-shrinkwrap.json</code>.</p> +data back to <code>package.json</code>, <code>package-lock.json</code>, and, if present, <code>npm-shrinkwrap.json</code>.</p> <p>The <code>newversion</code> argument should be a valid semver string, a valid second argument to <a href="https://github.com/npm/node-semver#functions">semver.inc</a> (one of <code>patch</code>, <code>minor</code>, <code>major</code>, <code>prepatch</code>, <code>preminor</code>, <code>premajor</code>, <code>prerelease</code>), or <code>from-git</code>. In the second case, @@ -120,5 +120,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.6.0</p> +<p id="footer">npm-version — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-view.html b/deps/npm/html/doc/cli/npm-view.html index a94ea56271..bde97a8e15 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.6.0</p> +<p id="footer">npm-view — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm-whoami.html b/deps/npm/html/doc/cli/npm-whoami.html index 5995b1e11c..3fe3ff115c 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.6.0</p> +<p id="footer">npm-whoami — npm@6.1.0</p> diff --git a/deps/npm/html/doc/cli/npm.html b/deps/npm/html/doc/cli/npm.html index 52f4a22544..50114e79e7 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.6.0</p> +<p>6.1.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 @@ -79,7 +79,7 @@ Use the <code>npm publish</code> command to upload your code to the registry.</l <ul> <li>Command line switches:<br>Set a config with <code>--key val</code>. All keys take a value, even if they are booleans (the config parser doesn't know what the options are at -the time of parsing.) If no value is provided, then the option is set +the time of parsing). If no value is provided, then the option is set to boolean <code>true</code>.</li> <li>Environment Variables:<br>Set any config by prefixing the name in an environment variable with <code>npm_config_</code>. For example, <code>export npm_config_key=val</code>.</li> @@ -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.6.0</p> +<p id="footer">npm — npm@6.1.0</p> diff --git a/deps/npm/html/doc/files/npm-folders.html b/deps/npm/html/doc/files/npm-folders.html index ff8a247b5a..0f85f255b2 100644 --- a/deps/npm/html/doc/files/npm-folders.html +++ b/deps/npm/html/doc/files/npm-folders.html @@ -58,7 +58,7 @@ when you run <code>npm test</code>.)</p> <p>Man pages are not installed on Windows systems.</p> <h3 id="cache">Cache</h3> <p>See <code><a href="../cli/npm-cache.html">npm-cache(1)</a></code>. Cache files are stored in <code>~/.npm</code> on Posix, or -<code>~/npm-cache</code> on Windows.</p> +<code>%AppData%/npm-cache</code> on Windows.</p> <p>This is controlled by the <code>cache</code> configuration param.</p> <h3 id="temp-files">Temp Files</h3> <p>Temporary files are stored by default in the folder specified by the @@ -135,15 +135,15 @@ highest level possible, below the localized "target" folder.</p> `-- baz (1.2.3) <---[D] `-- node_modules `-- quux (3.2.0) <---[E] -</code></pre><p>Since foo depends directly on <code>bar@1.2.3</code> and <code>baz@1.2.3</code>, those are -installed in foo's <code>node_modules</code> folder.</p> +</code></pre><p>Since foo depends directly on <a href="mailto:`bar@1.2.3">`bar@1.2.3</a><code>and</code><a href="mailto:baz@1.2.3">baz@1.2.3</a><code>, those are +installed in foo's</code>node_modules` folder.</p> <p>Even though the latest copy of blerg is 1.3.7, foo has a specific dependency on version 1.2.5. So, that gets installed at [A]. Since the -parent installation of blerg satisfies bar's dependency on <code>blerg@1.x</code>, +parent installation of blerg satisfies bar's dependency on <a href="mailto:`blerg@1.x">`blerg@1.x</a>`, it does not install another copy under [B].</p> <p>Bar [B] also has dependencies on baz and asdf, so those are installed in -bar's <code>node_modules</code> folder. Because it depends on <code>baz@2.x</code>, it cannot -re-use the <code>baz@1.2.3</code> installed in the parent <code>node_modules</code> folder [D], +bar's <code>node_modules</code> folder. Because it depends on <a href="mailto:`baz@2.x">`baz@2.x</a><code>, it cannot +re-use the</code><a href="mailto:baz@1.2.3">baz@1.2.3</a><code>installed in the parent</code>node_modules` folder [D], and must install its own copy [C].</p> <p>Underneath bar, the <code>baz -> quux -> bar</code> dependency creates a cycle. However, because bar is already in quux's ancestry [B], it does not @@ -181,5 +181,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.6.0</p> +<p id="footer">npm-folders — npm@6.1.0</p> diff --git a/deps/npm/html/doc/files/npm-global.html b/deps/npm/html/doc/files/npm-global.html index ff8a247b5a..0f85f255b2 100644 --- a/deps/npm/html/doc/files/npm-global.html +++ b/deps/npm/html/doc/files/npm-global.html @@ -58,7 +58,7 @@ when you run <code>npm test</code>.)</p> <p>Man pages are not installed on Windows systems.</p> <h3 id="cache">Cache</h3> <p>See <code><a href="../cli/npm-cache.html">npm-cache(1)</a></code>. Cache files are stored in <code>~/.npm</code> on Posix, or -<code>~/npm-cache</code> on Windows.</p> +<code>%AppData%/npm-cache</code> on Windows.</p> <p>This is controlled by the <code>cache</code> configuration param.</p> <h3 id="temp-files">Temp Files</h3> <p>Temporary files are stored by default in the folder specified by the @@ -135,15 +135,15 @@ highest level possible, below the localized "target" folder.</p> `-- baz (1.2.3) <---[D] `-- node_modules `-- quux (3.2.0) <---[E] -</code></pre><p>Since foo depends directly on <code>bar@1.2.3</code> and <code>baz@1.2.3</code>, those are -installed in foo's <code>node_modules</code> folder.</p> +</code></pre><p>Since foo depends directly on <a href="mailto:`bar@1.2.3">`bar@1.2.3</a><code>and</code><a href="mailto:baz@1.2.3">baz@1.2.3</a><code>, those are +installed in foo's</code>node_modules` folder.</p> <p>Even though the latest copy of blerg is 1.3.7, foo has a specific dependency on version 1.2.5. So, that gets installed at [A]. Since the -parent installation of blerg satisfies bar's dependency on <code>blerg@1.x</code>, +parent installation of blerg satisfies bar's dependency on <a href="mailto:`blerg@1.x">`blerg@1.x</a>`, it does not install another copy under [B].</p> <p>Bar [B] also has dependencies on baz and asdf, so those are installed in -bar's <code>node_modules</code> folder. Because it depends on <code>baz@2.x</code>, it cannot -re-use the <code>baz@1.2.3</code> installed in the parent <code>node_modules</code> folder [D], +bar's <code>node_modules</code> folder. Because it depends on <a href="mailto:`baz@2.x">`baz@2.x</a><code>, it cannot +re-use the</code><a href="mailto:baz@1.2.3">baz@1.2.3</a><code>installed in the parent</code>node_modules` folder [D], and must install its own copy [C].</p> <p>Underneath bar, the <code>baz -> quux -> bar</code> dependency creates a cycle. However, because bar is already in quux's ancestry [B], it does not @@ -181,5 +181,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.6.0</p> +<p id="footer">npm-folders — npm@6.1.0</p> diff --git a/deps/npm/html/doc/files/npm-json.html b/deps/npm/html/doc/files/npm-json.html index 3a6e77c981..42e47069f2 100644 --- a/deps/npm/html/doc/files/npm-json.html +++ b/deps/npm/html/doc/files/npm-json.html @@ -16,11 +16,11 @@ file. It must be actual JSON, not just a JavaScript object literal.</p> <p>A lot of the behavior described in this document is affected by the config settings described in <code><a href="../misc/npm-config.html">npm-config(7)</a></code>.</p> <h2 id="name">name</h2> -<p>The <em>most</em> important things in your package.json are the name and version fields. -Those are actually required, and your package won't install without -them. The name and version together form an identifier that is assumed -to be completely unique. Changes to the package should come along with -changes to the version.</p> +<p>If you plan to publish your package, the <em>most</em> important things in your +package.json are the name and version fields as they will be required. The name +and version together form an identifier that is assumed to be completely unique. +Changes to the package should come along with changes to the version. If you don't +plan to publish your package, the name and version fields are optional.</p> <p>The name is what your thing is called.</p> <p>Some rules:</p> <ul> @@ -45,11 +45,11 @@ already, before you get too attached to it. <a href="https://www.npmjs.com/">htt <p>A name can be optionally prefixed by a scope, e.g. <code>@myorg/mypackage</code>. See <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code> for more detail.</p> <h2 id="version">version</h2> -<p>The <em>most</em> important things in your package.json are the name and version fields. -Those are actually required, and your package won't install without -them. The name and version together form an identifier that is assumed -to be completely unique. Changes to the package should come along with -changes to the version.</p> +<p>If you plan to publish your package, the <em>most</em> important things in your +package.json are the name and version fields as they will be required. The name +and version together form an identifier that is assumed to be completely unique. +Changes to the package should come along with changes to the version. If you don't +plan to publish your package, the name and version fields are optional.</p> <p>Version must be parseable by <a href="https://github.com/isaacs/node-semver">node-semver</a>, which is bundled with npm as a dependency. (<code>npm install semver</code> to use it yourself.)</p> @@ -62,7 +62,9 @@ package, as it's listed in <code>npm search</code>.</p> discover your package as it's listed in <code>npm search</code>.</p> <h2 id="homepage">homepage</h2> <p>The url to the project homepage.</p> -<h2 id="bugs">bugs</h2> +<p>Example:</p> +<pre><code>"homepage": "https://github.com/owner/project#readme" +</code></pre><h2 id="bugs">bugs</h2> <p>The url to your project's issue tracker and / or the email address to which issues should be reported. These are helpful for people who encounter issues with your package.</p> @@ -129,13 +131,14 @@ is an object with a "name" field and optionally "url" and &q </code></pre><p>Both email and url are optional either way.</p> <p>npm also sets a top-level "maintainers" field with your npm user info.</p> <h2 id="files">files</h2> -<p>The optional "files" field is an array of file patterns that describes +<p>The optional <code>files</code> field is an array of file patterns that describes the entries to be included when your package is installed as a -dependency. If the files array is omitted, everything except -automatically-excluded files will be included in your publish. If you -name a folder in the array, then it will also include the files inside -that folder (unless they would be ignored by another rule in this -section.).</p> +dependency. File patterns follow a similar syntax to <code>.gitignore</code>, but +reversed: including a file, directory, or glob pattern (<code>*</code>, <code>**/*</code>, and such) +will make it so that file is included in the tarball when it's packed. Omitting +the field will make it default to <code>["*"]</code>, which means it will include all files.</p> +<p>Some special files and directories are also included or excluded regardless of +whether they exist in the <code>files</code> array (see below).</p> <p>You can also provide a <code>.npmignore</code> file in the root of your package or in subdirectories, which will keep files from being included. At the root of your package it will not override the "files" field, but in @@ -179,6 +182,10 @@ That is, if your package is named <code>foo</code>, and a user installs it, and <p>This should be a module ID relative to the root of your package folder.</p> <p>For most modules, it makes the most sense to have a main script and often not much else.</p> +<h2 id="browser">browser</h2> +<p>If your module is meant to be used client-side the browser field should be +used instead of the main field. This is helpful to hint users that it might +rely on primitives that aren't available in Node.js modules. (e.g. <code>window</code>)</p> <h2 id="bin">bin</h2> <p>A lot of packages have one or more executable files that they'd like to install into the PATH. npm makes this pretty easy (in fact, it uses this @@ -557,8 +564,8 @@ param at publish-time.</p> especially handy if you want to set the tag, registry or access, so that you can ensure that a given package is not tagged with "latest", published to the global public registry or that a scoped module is private by default.</p> -<p>Any config values can be overridden, but of course only "tag", "registry" and -"access" probably matter for the purposes of publishing.</p> +<p>Any config values can be overridden, but only "tag", "registry" and "access" +probably matter for the purposes of publishing.</p> <p>See <code><a href="../misc/npm-config.html">npm-config(7)</a></code> to see the list of config options that can be overridden.</p> <h2 id="default-values">DEFAULT VALUES</h2> @@ -603,5 +610,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.6.0</p> +<p id="footer">package.json — npm@6.1.0</p> diff --git a/deps/npm/html/doc/files/npm-package-locks.html b/deps/npm/html/doc/files/npm-package-locks.html index 775c6b4ca2..fe9115c14a 100644 --- a/deps/npm/html/doc/files/npm-package-locks.html +++ b/deps/npm/html/doc/files/npm-package-locks.html @@ -53,7 +53,7 @@ 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 +</code></pre><p>However, if <a href="mailto:B@0.0.2">B@0.0.2</a> is published, then a fresh <code>npm install A</code> will install:</p> <pre><code>A@0.1.0 `-- B@0.0.2 @@ -61,7 +61,7 @@ install:</p> </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 +could specify a dependency on <a href="mailto:B@0.0.1">B@0.0.1</a>. 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> @@ -125,6 +125,19 @@ 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> +<h3 id="resolving-lockfile-conflicts">Resolving lockfile conflicts</h3> +<p>Occasionally, two separate npm install will create package locks that cause +merge conflicts in source control systems. As of <a href="mailto:`npm@5.7.0">`npm@5.7.0</a><code>, these conflicts +can be resolved by manually fixing any</code>package.json<code>conflicts, and then +running</code>npm install [--package-lock-only]<code>again. npm will automatically +resolve any conflicts for you and write a merged package lock that includes all +the dependencies from both branches in a reasonable tree. If</code>--package-lock-only<code>is provided, it will do this without also modifying your +local</code>node_modules/`.</p> +<p>To make this process seamless on git, consider installing +<a href="https://npm.im/npm-merge-driver"><code>npm-merge-driver</code></a>, which will teach git how +to do this itself without any user interaction. In short: <code>$ npx +npm-merge-driver install -g</code> will let you do this, and even works with +<a href="mailto:pre-`npm@5.7.0">pre-`npm@5.7.0</a><code>versions of npm 5, albeit a bit more noisily. Note that if</code>package.json<code>itself conflicts, you will have to resolve that by hand and run</code>npm install` manually, even with the merge driver.</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> @@ -145,4 +158,4 @@ if any transitive dependencies were updated, hoisted, etc.</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-package-locks — npm@5.6.0</p> +<p id="footer">npm-package-locks — npm@6.1.0</p> diff --git a/deps/npm/html/doc/files/npm-shrinkwrap.json.html b/deps/npm/html/doc/files/npm-shrinkwrap.json.html index 50718ad9fd..1fca199c38 100644 --- a/deps/npm/html/doc/files/npm-shrinkwrap.json.html +++ b/deps/npm/html/doc/files/npm-shrinkwrap.json.html @@ -42,4 +42,4 @@ to the manual page for <a href="../files/package-lock.json.html">package-lock.js <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;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.6.0</p> +<p id="footer">npm-shrinkwrap.json — npm@6.1.0</p> diff --git a/deps/npm/html/doc/files/npmrc.html b/deps/npm/html/doc/files/npmrc.html index 7441c92b7e..e821a43090 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.6.0</p> +<p id="footer">npmrc — npm@6.1.0</p> diff --git a/deps/npm/html/doc/files/package-lock.json.html b/deps/npm/html/doc/files/package-lock.json.html index 3f6a2e21f5..fcce7979d7 100644 --- a/deps/npm/html/doc/files/package-lock.json.html +++ b/deps/npm/html/doc/files/package-lock.json.html @@ -103,12 +103,18 @@ 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="requires">requires</h4> +<p>This is a mapping of module name to version. This is a list of everything +this module requires, regardless of where it will be installed. The version +should match via normal matching rules a dependency either in our +<code>dependencies</code> or in a level higher than us.</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/npm-shrinkwrap.json.html">npm-shrinkwrap.json(5)</a></li> +<li><a href="../files/npm-package-locks.html">npm-package-locks(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> @@ -124,4 +130,4 @@ on the current platform.</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-lock.json — npm@5.6.0</p> +<p id="footer">package-lock.json — npm@6.1.0</p> diff --git a/deps/npm/html/doc/files/package.json.html b/deps/npm/html/doc/files/package.json.html index 3a6e77c981..42e47069f2 100644 --- a/deps/npm/html/doc/files/package.json.html +++ b/deps/npm/html/doc/files/package.json.html @@ -16,11 +16,11 @@ file. It must be actual JSON, not just a JavaScript object literal.</p> <p>A lot of the behavior described in this document is affected by the config settings described in <code><a href="../misc/npm-config.html">npm-config(7)</a></code>.</p> <h2 id="name">name</h2> -<p>The <em>most</em> important things in your package.json are the name and version fields. -Those are actually required, and your package won't install without -them. The name and version together form an identifier that is assumed -to be completely unique. Changes to the package should come along with -changes to the version.</p> +<p>If you plan to publish your package, the <em>most</em> important things in your +package.json are the name and version fields as they will be required. The name +and version together form an identifier that is assumed to be completely unique. +Changes to the package should come along with changes to the version. If you don't +plan to publish your package, the name and version fields are optional.</p> <p>The name is what your thing is called.</p> <p>Some rules:</p> <ul> @@ -45,11 +45,11 @@ already, before you get too attached to it. <a href="https://www.npmjs.com/">htt <p>A name can be optionally prefixed by a scope, e.g. <code>@myorg/mypackage</code>. See <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code> for more detail.</p> <h2 id="version">version</h2> -<p>The <em>most</em> important things in your package.json are the name and version fields. -Those are actually required, and your package won't install without -them. The name and version together form an identifier that is assumed -to be completely unique. Changes to the package should come along with -changes to the version.</p> +<p>If you plan to publish your package, the <em>most</em> important things in your +package.json are the name and version fields as they will be required. The name +and version together form an identifier that is assumed to be completely unique. +Changes to the package should come along with changes to the version. If you don't +plan to publish your package, the name and version fields are optional.</p> <p>Version must be parseable by <a href="https://github.com/isaacs/node-semver">node-semver</a>, which is bundled with npm as a dependency. (<code>npm install semver</code> to use it yourself.)</p> @@ -62,7 +62,9 @@ package, as it's listed in <code>npm search</code>.</p> discover your package as it's listed in <code>npm search</code>.</p> <h2 id="homepage">homepage</h2> <p>The url to the project homepage.</p> -<h2 id="bugs">bugs</h2> +<p>Example:</p> +<pre><code>"homepage": "https://github.com/owner/project#readme" +</code></pre><h2 id="bugs">bugs</h2> <p>The url to your project's issue tracker and / or the email address to which issues should be reported. These are helpful for people who encounter issues with your package.</p> @@ -129,13 +131,14 @@ is an object with a "name" field and optionally "url" and &q </code></pre><p>Both email and url are optional either way.</p> <p>npm also sets a top-level "maintainers" field with your npm user info.</p> <h2 id="files">files</h2> -<p>The optional "files" field is an array of file patterns that describes +<p>The optional <code>files</code> field is an array of file patterns that describes the entries to be included when your package is installed as a -dependency. If the files array is omitted, everything except -automatically-excluded files will be included in your publish. If you -name a folder in the array, then it will also include the files inside -that folder (unless they would be ignored by another rule in this -section.).</p> +dependency. File patterns follow a similar syntax to <code>.gitignore</code>, but +reversed: including a file, directory, or glob pattern (<code>*</code>, <code>**/*</code>, and such) +will make it so that file is included in the tarball when it's packed. Omitting +the field will make it default to <code>["*"]</code>, which means it will include all files.</p> +<p>Some special files and directories are also included or excluded regardless of +whether they exist in the <code>files</code> array (see below).</p> <p>You can also provide a <code>.npmignore</code> file in the root of your package or in subdirectories, which will keep files from being included. At the root of your package it will not override the "files" field, but in @@ -179,6 +182,10 @@ That is, if your package is named <code>foo</code>, and a user installs it, and <p>This should be a module ID relative to the root of your package folder.</p> <p>For most modules, it makes the most sense to have a main script and often not much else.</p> +<h2 id="browser">browser</h2> +<p>If your module is meant to be used client-side the browser field should be +used instead of the main field. This is helpful to hint users that it might +rely on primitives that aren't available in Node.js modules. (e.g. <code>window</code>)</p> <h2 id="bin">bin</h2> <p>A lot of packages have one or more executable files that they'd like to install into the PATH. npm makes this pretty easy (in fact, it uses this @@ -557,8 +564,8 @@ param at publish-time.</p> especially handy if you want to set the tag, registry or access, so that you can ensure that a given package is not tagged with "latest", published to the global public registry or that a scoped module is private by default.</p> -<p>Any config values can be overridden, but of course only "tag", "registry" and -"access" probably matter for the purposes of publishing.</p> +<p>Any config values can be overridden, but only "tag", "registry" and "access" +probably matter for the purposes of publishing.</p> <p>See <code><a href="../misc/npm-config.html">npm-config(7)</a></code> to see the list of config options that can be overridden.</p> <h2 id="default-values">DEFAULT VALUES</h2> @@ -603,5 +610,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.6.0</p> +<p id="footer">package.json — npm@6.1.0</p> diff --git a/deps/npm/html/doc/index.html b/deps/npm/html/doc/index.html index 914307420c..7a0db0c538 100644 --- a/deps/npm/html/doc/index.html +++ b/deps/npm/html/doc/index.html @@ -20,6 +20,8 @@ <p>Set access level on published packages</p> <h3 id="npm-adduser-1-"><a href="cli/npm-adduser.html">npm-adduser(1)</a></h3> <p>Add a registry user account</p> +<h3 id="npm-audit-1-"><a href="cli/npm-audit.html">npm-audit(1)</a></h3> +<p>Run a security audit</p> <h3 id="npm-bin-1-"><a href="cli/npm-bin.html">npm-bin(1)</a></h3> <p>Display npm bin folder</p> <h3 id="npm-bugs-1-"><a href="cli/npm-bugs.html">npm-bugs(1)</a></h3> @@ -30,6 +32,8 @@ <p>REMOVED</p> <h3 id="npm-cache-1-"><a href="cli/npm-cache.html">npm-cache(1)</a></h3> <p>Manipulates packages cache</p> +<h3 id="npm-ci-1-"><a href="cli/npm-ci.html">npm-ci(1)</a></h3> +<p>Install a project with a clean slate</p> <h3 id="npm-completion-1-"><a href="cli/npm-completion.html">npm-completion(1)</a></h3> <p>Tab Completion for npm</p> <h3 id="npm-config-1-"><a href="cli/npm-config.html">npm-config(1)</a></h3> @@ -52,8 +56,12 @@ <p>Search npm help documentation</p> <h3 id="npm-help-1-"><a href="cli/npm-help.html">npm-help(1)</a></h3> <p>Get help on npm</p> +<h3 id="npm-hook-1-"><a href="cli/npm-hook.html">npm-hook(1)</a></h3> +<p>Manage registry hooks</p> <h3 id="npm-init-1-"><a href="cli/npm-init.html">npm-init(1)</a></h3> -<p>Interactively create a package.json file</p> +<p>create a package.json file</p> +<h3 id="npm-install-ci-test-1-"><a href="cli/npm-install-ci-test.html">npm-install-ci-test(1)</a></h3> +<p>Install a project with a clean slate and run tests</p> <h3 id="npm-install-test-1-"><a href="cli/npm-install-test.html">npm-install-test(1)</a></h3> <p>Install package(s) and run tests</p> <h3 id="npm-install-1-"><a href="cli/npm-install.html">npm-install(1)</a></h3> @@ -172,5 +180,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.6.0</p> +<p id="footer">npm-index — npm@6.1.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 f96dd270bf..204556e25a 100644 --- a/deps/npm/html/doc/misc/npm-coding-style.html +++ b/deps/npm/html/doc/misc/npm-coding-style.html @@ -91,7 +91,7 @@ final token in the list on a line by itself. For example:</p> <pre><code>var ok = 'String contains "double" quotes' var alsoOk = "String contains 'single' quotes or apostrophe" </code></pre><h2 id="whitespace">Whitespace</h2> -<p>Put a single space in front of ( for anything other than a function call. +<p>Put a single space in front of <code>(</code> for anything other than a function call. Also use a single space wherever it makes things more readable.</p> <p>Don't leave trailing whitespace at the end of lines. Don't indent empty lines. Don't use more spaces than are helpful.</p> @@ -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.6.0</p> +<p id="footer">npm-coding-style — npm@6.1.0</p> diff --git a/deps/npm/html/doc/misc/npm-config.html b/deps/npm/html/doc/misc/npm-config.html index a23b10727a..0abd19a970 100644 --- a/deps/npm/html/doc/misc/npm-config.html +++ b/deps/npm/html/doc/misc/npm-config.html @@ -134,6 +134,14 @@ even for <code>GET</code> requests.</p> </ul> <p>When "dev" or "development" and running local <code>npm shrinkwrap</code>, <code>npm outdated</code>, or <code>npm update</code>, is an alias for <code>--dev</code>.</p> +<h3 id="audit">audit</h3> +<ul> +<li>Default: true</li> +<li>Type: Boolean</li> +</ul> +<p>When "true" submit audit reports alongside <code>npm install</code> runs to the default +registry and all registries configured for scopes. See the documentation +for <a href="../cli/npm-audit.html">npm-audit(1)</a> for details on what is submitted.</p> <h3 id="auth-type">auth-type</h3> <ul> <li>Default: <code>'legacy'</code></li> @@ -239,6 +247,8 @@ PEM format (Windows calls it "Base-64 encoded X.509 (.CER)") with newl </ul> <p>If false, never shows colors. If <code>"always"</code> then always shows colors. If true, then only prints color codes for tty file descriptors.</p> +<p>This option can also be changed using the environment: colors are +disabled when the environment variable <code>NO_COLOR</code> is set to any value.</p> <h3 id="depth">depth</h3> <ul> <li>Default: Infinity</li> @@ -560,7 +570,7 @@ combination). Passed to the <code>http</code> <code>Agent</code> used to make th <p>Any "%s" in the message will be replaced with the version number.</p> <h3 id="metrics-registry">metrics-registry</h3> <ul> -<li>Default: The value of <code>registry</code> (which defaults to "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>")</li> +<li>Default: The value of <code>registry</code> (which defaults to "<a href="https://registry.npmjs.org/"">https://registry.npmjs.org/"</a>)</li> <li>Type: String</li> </ul> <p>The registry you want to send cli metrics to if <code>send-metrics</code> is true.</p> @@ -578,6 +588,12 @@ impact how lifecycle scripts are called.</p> <li>Type: semver or false</li> </ul> <p>The node version to use when checking a package's <code>engines</code> map.</p> +<h3 id="no-proxy">no-proxy</h3> +<ul> +<li>Default: null</li> +<li>Type: String or Array</li> +</ul> +<p>A comma-separated string or an array of domain extensions that a proxy should not be used for.</p> <h3 id="offline">offline</h3> <ul> <li>Default: false</li> @@ -628,13 +644,16 @@ when publishing or changing package permissions with <code>npm access</code>.</p </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>When package package-locks are disabled, automatic pruning of extraneous +modules will also be disabled. To remove extraneous modules with +package-locks disabled use <code>npm prune</code>.</p> <p>This option is an alias for <code>--shrinkwrap</code>.</p> <h3 id="package-lock-only">package-lock-only</h3> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> -<p>If set to true, it will update only the <code>package-json</code>, +<p>If set to true, it will update only the <code>package-lock.json</code>, instead of checking <code>node_modules</code> and downloading dependencies.</p> <h3 id="parseable">parseable</h3> <ul> @@ -718,7 +737,7 @@ honored by the underlying <code>request</code> library.</p> <p>Remove failed installs.</p> <h3 id="save">save</h3> <ul> -<li>Default: false</li> +<li>Default: true</li> <li>Type: Boolean</li> </ul> <p>Save installed packages to a package.json file as dependencies.</p> @@ -1024,5 +1043,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.6.0</p> +<p id="footer">npm-config — npm@6.1.0</p> diff --git a/deps/npm/html/doc/misc/npm-developers.html b/deps/npm/html/doc/misc/npm-developers.html index bdf212ed4b..526bcc6d34 100644 --- a/deps/npm/html/doc/misc/npm-developers.html +++ b/deps/npm/html/doc/misc/npm-developers.html @@ -20,7 +20,7 @@ that your users will do to install your program.</p> <p>These are man pages. If you install npm, you should be able to then do <code>man npm-thing</code> to get the documentation on a particular topic, or <code>npm help thing</code> to see the same information.</p> -<h2 id="what-is-a-package-">What is a <code>package</code></h2> +<h2 id="what-is-a-package">What is a <code>package</code></h2> <p>A package is:</p> <ul> <li>a) a folder containing a program described by a package.json file</li> @@ -53,7 +53,7 @@ This should be a string that identifies your project. Please do not use the name to specify that it runs on node, or is in JavaScript. You can use the "engines" field to explicitly state the versions of node (or whatever else) that your program requires, and it's pretty -well assumed that it's javascript.</p> +well assumed that it's JavaScript.</p> <p>It does not necessarily need to match your github repository name.</p> <p>So, <code>node-foo</code> and <code>bar-js</code> are bad names. <code>foo</code> or <code>bar</code> are better.</p> </li> @@ -204,5 +204,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.6.0</p> +<p id="footer">npm-developers — npm@6.1.0</p> diff --git a/deps/npm/html/doc/misc/npm-disputes.html b/deps/npm/html/doc/misc/npm-disputes.html index fdf53fcad0..543a601979 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> @@ -44,7 +44,7 @@ publishes it to the npm registry. Being a simple little thing, it never really has to be updated. Alice works for Foo Inc, the makers of the critically acclaimed and widely-marketed <code>foo</code> JavaScript toolkit framework. They publish it to npm as <code>foojs</code>, but people are routinely confused when -<code>npm install</code>foo`` is some different thing.</li> +<code>npm install</code>foo<code></code> is some different thing.</li> <li><p>Yusuf writes a parser for the widely-known <code>foo</code> file format, because he needs it for work. Then, he gets a new job, and never updates the prototype. Later on, Alice writes a much more complete <code>foo</code> parser, but can't publish, @@ -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.6.0</p> +<p id="footer">npm-disputes — npm@6.1.0</p> diff --git a/deps/npm/html/doc/misc/npm-index.html b/deps/npm/html/doc/misc/npm-index.html index 927748e176..d3c382a203 100644 --- a/deps/npm/html/doc/misc/npm-index.html +++ b/deps/npm/html/doc/misc/npm-index.html @@ -20,6 +20,8 @@ <p>Set access level on published packages</p> <h3 id="npm-adduser-1-"><a href="../cli/npm-adduser.html">npm-adduser(1)</a></h3> <p>Add a registry user account</p> +<h3 id="npm-audit-1-"><a href="../cli/npm-audit.html">npm-audit(1)</a></h3> +<p>Run a security audit</p> <h3 id="npm-bin-1-"><a href="../cli/npm-bin.html">npm-bin(1)</a></h3> <p>Display npm bin folder</p> <h3 id="npm-bugs-1-"><a href="../cli/npm-bugs.html">npm-bugs(1)</a></h3> @@ -30,6 +32,8 @@ <p>REMOVED</p> <h3 id="npm-cache-1-"><a href="../cli/npm-cache.html">npm-cache(1)</a></h3> <p>Manipulates packages cache</p> +<h3 id="npm-ci-1-"><a href="../cli/npm-ci.html">npm-ci(1)</a></h3> +<p>Install a project with a clean slate</p> <h3 id="npm-completion-1-"><a href="../cli/npm-completion.html">npm-completion(1)</a></h3> <p>Tab Completion for npm</p> <h3 id="npm-config-1-"><a href="../cli/npm-config.html">npm-config(1)</a></h3> @@ -52,8 +56,12 @@ <p>Search npm help documentation</p> <h3 id="npm-help-1-"><a href="../cli/npm-help.html">npm-help(1)</a></h3> <p>Get help on npm</p> +<h3 id="npm-hook-1-"><a href="../cli/npm-hook.html">npm-hook(1)</a></h3> +<p>Manage registry hooks</p> <h3 id="npm-init-1-"><a href="../cli/npm-init.html">npm-init(1)</a></h3> -<p>Interactively create a package.json file</p> +<p>create a package.json file</p> +<h3 id="npm-install-ci-test-1-"><a href="../cli/npm-install-ci-test.html">npm-install-ci-test(1)</a></h3> +<p>Install a project with a clean slate and run tests</p> <h3 id="npm-install-test-1-"><a href="../cli/npm-install-test.html">npm-install-test(1)</a></h3> <p>Install package(s) and run tests</p> <h3 id="npm-install-1-"><a href="../cli/npm-install.html">npm-install(1)</a></h3> @@ -172,5 +180,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.6.0</p> +<p id="footer">npm-index — npm@6.1.0</p> diff --git a/deps/npm/html/doc/misc/npm-orgs.html b/deps/npm/html/doc/misc/npm-orgs.html index 5a11a10ca8..3ed6709f33 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.6.0</p> +<p id="footer">npm-orgs — npm@6.1.0</p> diff --git a/deps/npm/html/doc/misc/npm-registry.html b/deps/npm/html/doc/misc/npm-registry.html index cfa610d0e8..f3f9704a87 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.6.0</p> +<p id="footer">npm-registry — npm@6.1.0</p> diff --git a/deps/npm/html/doc/misc/npm-scope.html b/deps/npm/html/doc/misc/npm-scope.html index e610f3e9e3..7c285406b2 100644 --- a/deps/npm/html/doc/misc/npm-scope.html +++ b/deps/npm/html/doc/misc/npm-scope.html @@ -60,7 +60,7 @@ the initial publication. This will publish the package and set access to <code>public</code> as if you had run <code>npm access public</code> after publishing.</p> <h3 id="publishing-private-scoped-packages-to-the-npm-registry">Publishing private scoped packages to the npm registry</h3> <p>To publish a private scoped package to the npm registry, you must have -an <a href="https://www.npmjs.com/private-modules">npm Private Modules</a> +an <a href="https://docs.npmjs.com/private-modules/intro">npm Private Modules</a> account.</p> <p>You can then publish the module with <code>npm publish</code> or <code>npm publish --access restricted</code>, and it will be present in the npm registry, with @@ -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.6.0</p> +<p id="footer">npm-scope — npm@6.1.0</p> diff --git a/deps/npm/html/doc/misc/npm-scripts.html b/deps/npm/html/doc/misc/npm-scripts.html index bc43c028f1..43b0ca63e0 100644 --- a/deps/npm/html/doc/misc/npm-scripts.html +++ b/deps/npm/html/doc/misc/npm-scripts.html @@ -64,15 +64,15 @@ names will be run for those as well (e.g. <code>premyscript</code>, <code>myscri <p><pkg> -- npm run <stage>`.</p> <h2 id="prepublish-and-prepare">PREPUBLISH AND PREPARE</h2> <h3 id="deprecation-note">DEPRECATION NOTE</h3> -<p>Since <code>npm@1.1.71</code>, the npm CLI has run the <code>prepublish</code> script for both <code>npm -publish</code> and <code>npm install</code>, because it's a convenient way to prepare a package +<p>Since <a href="mailto:`npm@1.1.71">`npm@1.1.71</a><code>, the npm CLI has run the</code>prepublish<code>script for both</code>npm +publish<code>and</code>npm install<code>, because it's a convenient way to prepare a package for use (some common use cases are described in the section below). It has -also turned out to be, in practice, <a href="https://github.com/npm/npm/issues/10074">very -confusing</a>. As of <code>npm@4.0.0</code>, a new -event has been introduced, <code>prepare</code>, that preserves this existing behavior. A -<em>new</em> event, <code>prepublishOnly</code> has been added as a transitional strategy to +also turned out to be, in practice, [very +confusing](https://github.com/npm/npm/issues/10074). As of</code><a href="mailto:npm@4.0.0">npm@4.0.0</a><code>, a new +event has been introduced,</code>prepare<code>, that preserves this existing behavior. A +_new_ event,</code>prepublishOnly<code>has been added as a transitional strategy to allow users to avoid the confusing behavior of existing npm versions and only -run on <code>npm publish</code> (for instance, running the tests one last time to ensure +run on</code>npm publish` (for instance, running the tests one last time to ensure they're in good shape).</p> <p>See <a href="https://github.com/npm/npm/issues/10074">https://github.com/npm/npm/issues/10074</a> for a much lengthier justification, with further reading, for this change.</p> @@ -239,5 +239,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.6.0</p> +<p id="footer">npm-scripts — npm@6.1.0</p> diff --git a/deps/npm/html/doc/misc/removing-npm.html b/deps/npm/html/doc/misc/removing-npm.html index 1727455c62..15077119ab 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.6.0</p> +<p id="footer">removing-npm — npm@6.1.0</p> diff --git a/deps/npm/html/doc/misc/semver.html b/deps/npm/html/doc/misc/semver.html index afe72d3099..b3a69fbce3 100644 --- a/deps/npm/html/doc/misc/semver.html +++ b/deps/npm/html/doc/misc/semver.html @@ -24,6 +24,8 @@ semver.clean(' =v1.2.3 ') // '1.2.3' semver.satisfies('1.2.3', '1.x || >=2.5.0 || 5.0.0 - 7.2.3') // true semver.gt('1.2.3', '9.8.7') // false semver.lt('1.2.3', '9.8.7') // true +semver.valid(semver.coerce('v2')) // '2.0.0' +semver.valid(semver.coerce('42.6.7.9.3-alpha')) // '42.6.7' </code></pre> <p>As a command-line utility:</p> <pre><code>$ semver -h @@ -53,6 +55,10 @@ Options: -l --loose Interpret versions and ranges loosely +-c --coerce + Coerce a string into SemVer if possible + (does not imply --loose) + Program exits successfully if any valid version satisfies all supplied ranges, and prints all satisfying versions. @@ -133,7 +139,7 @@ will append the value of the string as a prerelease identifier:</p> deterministic ways.</p> <p>Advanced ranges may be combined in the same way as primitive comparators using white space or <code>||</code>.</p> -<h4 id="hyphen-ranges-x-y-z-a-b-c-">Hyphen Ranges <code>X.Y.Z - A.B.C</code></h4> +<h4 id="hyphen-ranges-x-y-z-a-b-c">Hyphen Ranges <code>X.Y.Z - A.B.C</code></h4> <p>Specifies an inclusive set.</p> <ul> <li><code>1.2.3 - 2.3.4</code> := <code>>=1.2.3 <=2.3.4</code></li> @@ -166,7 +172,7 @@ character is in fact optional.</p> <li><code>1</code> := <code>1.x.x</code> := <code>>=1.0.0 <2.0.0</code></li> <li><code>1.2</code> := <code>1.2.x</code> := <code>>=1.2.0 <1.3.0</code></li> </ul> -<h4 id="tilde-ranges-1-2-3-1-2-1-">Tilde Ranges <code>~1.2.3</code> <code>~1.2</code> <code>~1</code></h4> +<h4 id="tilde-ranges-1-2-3-1-2-1">Tilde Ranges <code>~1.2.3</code> <code>~1.2</code> <code>~1</code></h4> <p>Allows patch-level changes if a minor version is specified on the comparator. Allows minor-level changes if not.</p> <ul> @@ -182,7 +188,7 @@ equal to <code>beta.2</code>. So, <code>1.2.3-beta.4</code> would be allowed, b <code>1.2.4-beta.2</code> would not, because it is a prerelease of a different <code>[major, minor, patch]</code> tuple.</li> </ul> -<h4 id="caret-ranges-1-2-3-0-2-5-0-0-4-">Caret Ranges <code>^1.2.3</code> <code>^0.2.5</code> <code>^0.0.4</code></h4> +<h4 id="caret-ranges-1-2-3-0-2-5-0-0-4">Caret Ranges <code>^1.2.3</code> <code>^0.2.5</code> <code>^0.0.4</code></h4> <p>Allows changes that do not modify the left-most non-zero digit in the <code>[major, minor, patch]</code> tuple. In other words, this allows patch and minor updates for versions <code>1.0.0</code> and above, patch updates for @@ -324,6 +330,21 @@ range (since <code>1.2.8</code> satisfies, which is lower), and it also does not satisfy the range.</p> <p>If you want to know if a version satisfies or does not satisfy a range, use the <code>satisfies(version, range)</code> function.</p> +<h3 id="coercion">Coercion</h3> +<ul> +<li><code>coerce(version)</code>: Coerces a string to semver if possible</li> +</ul> +<p>This aims to provide a very forgiving translation of a non-semver +string to semver. It looks for the first digit in a string, and +consumes all remaining characters which satisfy at least a partial semver +(e.g., <code>1</code>, <code>1.2</code>, <code>1.2.3</code>) up to the max permitted length (256 characters). +Longer versions are simply truncated (<code>4.6.3.9.2-alpha2</code> becomes <code>4.6.3</code>). +All surrounding text is simply ignored (<code>v3.4 replaces v3.3.1</code> becomes <code>3.4.0</code>). +Only text which lacks digits will fail coercion (<code>version one</code> is not valid). +The maximum length for any semver component considered for coercion is 16 characters; +longer components will be ignored (<code>10000000000000000.4.7.4</code> becomes <code>4.7.4</code>). +The maximum value for any semver component is <code>Integer.MAX_SAFE_INTEGER || (2**53 - 1)</code>; +higher value components are invalid (<code>9999999999999999.4.7.4</code> is likely invalid).</p> </div> @@ -336,5 +357,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.6.0</p> +<p id="footer">semver — npm@6.1.0</p> |