deps: upgrade npm to 7.14.0

PR-URL: https://github.com/nodejs/node/pull/38750
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Reviewed-By: Beth Griggs <bgriggs@redhat.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>

1 files changed, 34 insertions, 13 deletions

diff --git a/deps/npm/docs/output/using-npm/config.html b/deps/npm/docs/output/using-npm/config.html
index 881080eb121..7e722bdc187 100644
--- a/deps/npm/docs/output/using-npm/config.html
+++ b/deps/npm/docs/output/using-npm/config.html
@@ -553,6 +553,7 @@ different version of <code>node</code>, even if <code>--engine-strict</code> is
 range (including SemVer-major changes).</li>
 <li>Allow unpublishing all versions of a published package.</li>
 <li>Allow conflicting peerDependencies to be installed in the root project.</li>
+<li>Implicitly set <code>--yes</code> during <code>npm init</code>.</li>
 </ul>
 <p>If you don’t have a clear idea of what you want to do, it is strongly
 recommended that you do not use this option!</p>
@@ -657,6 +658,10 @@ CI setup.</p>
 <li>Type: Boolean</li>
 </ul>
 <p>If true, npm does not run scripts specified in package.json files.</p>
+<p>Note that commands explicitly intended to run a particular script, such as
+<code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code>
+will still run their intended script if <code>ignore-scripts</code> is set, but they
+will <em>not</em> run any pre- or post-scripts.</p>
 <h4 id="include"><code>include</code></h4>
 <ul>
 <li>Default:</li>
@@ -721,10 +726,7 @@ number, if not already set in package.json.</p>
 <li>Type: Boolean</li>
 </ul>
 <p>Whether or not to output JSON data, rather than the normal output.</p>
-<p>This feature is currently experimental, and the output data structures for
-many commands is either not implemented in JSON yet, or subject to change.
-Only the output from <code>npm ls --json</code> and <code>npm search --json</code> are currently
-valid.</p>
+<p>Not supported by all npm commands.</p>
 <h4 id="key"><code>key</code></h4>
 <ul>
 <li>Default: null</li>
@@ -773,6 +775,7 @@ two conditions are met:</p>
 <li>the globally installed version is identical to the version that is being
 installed locally.</li>
 </ul>
+<p>When used with <code>npm ls</code>, only show packages that are linked.</p>
 <h4 id="local-address"><code>local-address</code></h4>
 <ul>
 <li>Default: null</li>
@@ -801,7 +804,7 @@ npm registry. Must be IPv4 in versions of Node prior to 0.12.</p>
 <li>Default: false</li>
 <li>Type: Boolean</li>
 </ul>
-<p>Show extended information in <code>npm ls</code> and <code>npm search</code>.</p>
+<p>Show extended information in <code>ls</code>, <code>search</code>, and <code>help-search</code>.</p>
 <h4 id="maxsockets"><code>maxsockets</code></h4>
 <ul>
 <li>Default: 15</li>
@@ -852,8 +855,8 @@ how lifecycle scripts are called.</p>
 allow the CLI to fill in missing cache data, see <code>--prefer-offline</code>.</p>
 <h4 id="omit"><code>omit</code></h4>
 <ul>
-<li>Default: ‘dev’ if the NODE_ENV environment variable is set to ‘production’,
-otherwise empty.</li>
+<li>Default: ‘dev’ if the <code>NODE_ENV</code> environment variable is set to
+‘production’, otherwise empty.</li>
 <li>Type: “dev”, “optional”, or “peer” (can be set multiple times)</li>
 </ul>
 <p>Dependency types to omit from the installation tree on disk.</p>
@@ -1037,12 +1040,21 @@ or <code>--save-optional</code> are true.</p>
 <li>Type: String</li>
 </ul>
 <p>Associate an operation with a scope for a scoped registry.</p>
-<p>Useful when logging in to a private registry for the first time:</p>
-<pre lang="bash"><code>npm login --scope=@mycorp --registry=https://registry.mycorp.com
+<p>Useful when logging in to or out of a private registry:</p>
+<pre><code># log in, linking the scope to the custom registry
+npm login --scope=@mycorp --registry=https://registry.mycorp.com
+
+# log out, removing the link and the auth token
+npm logout --scope=@mycorp
 </code></pre>
 <p>This will cause <code>@mycorp</code> to be mapped to the registry for future
 installation of packages specified according to the pattern
 <code>@mycorp/package</code>.</p>
+<p>This will also cause <code>npm init</code> to create a scoped package.</p>
+<pre><code># accept all defaults, and create a package named "@foo/whatever",
+# instead of just named "whatever"
+npm init --scope=@foo --yes
+</code></pre>
 <h4 id="script-shell"><code>script-shell</code></h4>
 <ul>
 <li>Default: ‘/bin/sh’ on POSIX systems, ‘cmd.exe’ on Windows</li>
@@ -1133,6 +1145,8 @@ via https.</p>
 then it will install the specified tag.</p>
 <p>Also the tag that is added to the package@version specified by the <code>npm tag</code>
 command, if no explicit tag is given.</p>
+<p>When used by the <code>npm diff</code> command, this is the tag used to fetch the
+tarball that will be compared with the local files by default.</p>
 <h4 id="tag-version-prefix"><code>tag-version-prefix</code></h4>
 <ul>
 <li>Default: “v”</li>
@@ -1173,7 +1187,7 @@ other files are created with a mode of 0o644.</p>
 <h4 id="unicode"><code>unicode</code></h4>
 <ul>
 <li>Default: false on windows, true on mac/unix systems with a unicode locale,
-as defined by the LC_ALL, LC_CTYPE, or LANG environment variables.</li>
+as defined by the <code>LC_ALL</code>, <code>LC_CTYPE</code>, or <code>LANG</code> environment variables.</li>
 <li>Type: Boolean</li>
 </ul>
 <p>When set to true, npm uses unicode characters in the tree output. When
@@ -1255,9 +1269,16 @@ exists, and exit successfully.</p>
 <p>Enable running a command in the context of the configured workspaces of the
 current project while filtering by running only the workspaces defined by
 this configuration option.</p>
-<p>Valid values for the <code>workspace</code> config are either: - Workspace names - Path
-to a workspace directory - Path to a parent workspace directory (will result
-to selecting all of the nested workspaces)</p>
+<p>Valid values for the <code>workspace</code> config are either:</p>
+<ul>
+<li>Workspace names</li>
+<li>Path to a workspace directory</li>
+<li>Path to a parent workspace directory (will result to selecting all of the
+nested workspaces)</li>
+</ul>
+<p>When set for the <code>npm init</code> command, this may be set to the folder of a
+workspace which does not yet exist, to create the folder and set it up as a
+brand new workspace within the project.</p>
 <p>This value is not exported to the environment for child processes.</p>
 <h4 id="workspaces"><code>workspaces</code></h4>
 <ul>