diff options
| author | npm team <ops+robot@npmjs.com> | 2021-07-27 19:39:44 +0300 |
|---|---|---|
| committer | Myles Borins <mylesborins@github.com> | 2021-07-29 00:16:31 +0300 |
| commit | 3a10a37f28020ac7353609990b5ddda8673f81d1 (patch) | |
| tree | 401d90c046ebdc96f0f7570245dc40312d8d0ce6 /deps/npm/docs/output | |
| parent | fea3357b7f996061adf47315856c9c7e2e5df0e1 (diff) | |
deps: upgrade npm to 7.20.2
PR-URL: https://github.com/nodejs/node/pull/39549
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Beth Griggs <bgriggs@redhat.com>
Reviewed-By: Ruy Adorno <ruyadorno@github.com>
Diffstat (limited to 'deps/npm/docs/output')
| -rw-r--r-- | deps/npm/docs/output/commands/npm-ls.html | 2 | ||||
| -rw-r--r-- | deps/npm/docs/output/commands/npm-pkg.html | 2 | ||||
| -rw-r--r-- | deps/npm/docs/output/commands/npm.html | 4 | ||||
| -rw-r--r-- | deps/npm/docs/output/using-npm/registry.html | 2 |
4 files changed, 5 insertions, 5 deletions
diff --git a/deps/npm/docs/output/commands/npm-ls.html b/deps/npm/docs/output/commands/npm-ls.html index 8af88b78dd5..6b62ca7266c 100644 --- a/deps/npm/docs/output/commands/npm-ls.html +++ b/deps/npm/docs/output/commands/npm-ls.html @@ -159,7 +159,7 @@ tree at all, use <a href="../commands/npm-explain.html"><code>npm explain</code> 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 lang="bash"><code>npm@7.20.0 /path/to/npm +<pre lang="bash"><code>npm@7.20.2 /path/to/npm └─┬ init-package-json@0.0.4 └── promzard@0.1.5 </code></pre> diff --git a/deps/npm/docs/output/commands/npm-pkg.html b/deps/npm/docs/output/commands/npm-pkg.html index 1f8a86e76e5..f837cb310a6 100644 --- a/deps/npm/docs/output/commands/npm-pkg.html +++ b/deps/npm/docs/output/commands/npm-pkg.html @@ -152,7 +152,7 @@ npm pkg delete <field> [.<subfield> ...] <h3 id="description">Description</h3> <p>A command that automates the management of <code>package.json</code> files. <code>npm pkg</code> provide 3 different sub commands that allow you to modify or retrieve -values for given object keys in your <code>packge.json</code>.</p> +values for given object keys in your <code>package.json</code>.</p> <p>The syntax to retrieve and set fields is a dot separated representation of the nested object properties to be found within your <code>package.json</code>, it’s the same notation used in <a href="../commands/npm-view.html"><code>npm view</code></a> to retrieve information diff --git a/deps/npm/docs/output/commands/npm.html b/deps/npm/docs/output/commands/npm.html index e5e0b82ad35..bfb8a6c4843 100644 --- a/deps/npm/docs/output/commands/npm.html +++ b/deps/npm/docs/output/commands/npm.html @@ -148,7 +148,7 @@ npm command-line interface <pre lang="bash"><code>npm <command> [args] </code></pre> <h3 id="version">Version</h3> -<p>7.20.0</p> +<p>7.20.2</p> <h3 id="description">Description</h3> <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 @@ -161,7 +161,7 @@ programs.</p> <p>npm comes preconfigured to use npm’s public registry at <a href="https://registry.npmjs.org">https://registry.npmjs.org</a> by default. Use of the npm public registry is subject to terms of use available at -<a href="https://www.npmjs.com/policies/terms">https://www.npmjs.com/policies/terms</a>.</p> +<a href="https://docs.npmjs.com/policies/terms">https://docs.npmjs.com/policies/terms</a>.</p> <p>You can configure npm to use any compatible registry you like, and even run your own registry. Use of someone else’s registry is governed by their terms of use.</p> diff --git a/deps/npm/docs/output/using-npm/registry.html b/deps/npm/docs/output/using-npm/registry.html index 451b9ac5338..3514ac72cd4 100644 --- a/deps/npm/docs/output/using-npm/registry.html +++ b/deps/npm/docs/output/using-npm/registry.html @@ -150,7 +150,7 @@ that implements the CommonJS Package Registry specification for reading package info.</p> <p>npm is configured to use the <strong>npm public registry</strong> at <a href="https://registry.npmjs.org">https://registry.npmjs.org</a> by default. Use of the npm public registry is -subject to terms of use available at <a href="https://www.npmjs.com/policies/terms">https://www.npmjs.com/policies/terms</a>.</p> +subject to terms of use available at <a href="https://docs.npmjs.com/policies/terms">https://docs.npmjs.com/policies/terms</a>.</p> <p>You can configure npm to use any compatible registry you like, and even run your own registry. Use of someone else’s registry may be governed by their terms of use.</p> |