deps: upgrade npm to 7.3.0

PR-URL: https://github.com/nodejs/node/pull/36572
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>

5 files changed, 55 insertions, 35 deletions

diff --git a/deps/npm/docs/output/commands/npm-config.html b/deps/npm/docs/output/commands/npm-config.html
index cce9963f571..92456282278 100644
--- a/deps/npm/docs/output/commands/npm-config.html
+++ b/deps/npm/docs/output/commands/npm-config.html
@@ -145,15 +145,15 @@ npm command-line interface
 </section>
 
 <div id="_content"><h3 id="synopsis">Synopsis</h3>
-<pre lang="bash"><code>npm config set &lt;key&gt; &lt;value&gt; [-g|--global]
-npm config get &lt;key&gt;
-npm config delete &lt;key&gt;
-npm config list [-l] [--json]
+<pre lang="bash"><code>npm config set &lt;key&gt;=&lt;value&gt; [&lt;key&gt;=&lt;value&gt; ...]
+npm config get [&lt;key&gt; [&lt;key&gt; ...]]
+npm config delete &lt;key&gt; [&lt;key&gt; ...]
+npm config list [--json]
 npm config edit
-npm get &lt;key&gt;
-npm set &lt;key&gt; &lt;value&gt; [-g|--global]
+npm set &lt;key&gt;=&lt;value&gt; [&lt;key&gt;=&lt;value&gt; ...]
+npm get [&lt;key&gt; [&lt;key&gt; ...]]
 
-aliases: c
+alias: c
 </code></pre>
 <h3 id="description">Description</h3>
 <p>npm gets its config settings from the command line, environment
@@ -167,23 +167,30 @@ of the user and global npmrc files.</p>
 <h3 id="sub-commands">Sub-commands</h3>
 <p>Config supports the following sub-commands:</p>
 <h4 id="set">set</h4>
-<pre lang="bash"><code>npm config set key value
+<pre lang="bash"><code>npm config set key=value [key=value...]
+npm set key=value [key=value...]
 </code></pre>
-<p>Sets the config key to the value.</p>
-<p>If value is omitted, then it sets it to “true”.</p>
+<p>Sets each of the config keys to the value provided.</p>
+<p>If value is omitted, then it sets it to an empty string.</p>
+<p>Note: for backwards compatibility, <code>npm config set key value</code> is supported
+as an alias for <code>npm config set key=value</code>.</p>
 <h4 id="get">get</h4>
-<pre lang="bash"><code>npm config get key
+<pre lang="bash"><code>npm config get [key ...]
+npm get [key ...]
 </code></pre>
-<p>Echo the config value to stdout.</p>
+<p>Echo the config value(s) to stdout.</p>
+<p>If multiple keys are provided, then the values will be prefixed with the
+key names.</p>
+<p>If no keys are provided, then this command behaves the same as <code>npm config list</code>.</p>
 <h4 id="list">list</h4>
 <pre lang="bash"><code>npm config list
 </code></pre>
 <p>Show all the config settings. Use <code>-l</code> to also show defaults. Use <code>--json</code>
 to show the settings in json format.</p>
 <h4 id="delete">delete</h4>
-<pre lang="bash"><code>npm config delete key
+<pre lang="bash"><code>npm config delete key [key ...]
 </code></pre>
-<p>Deletes the key from all configuration files.</p>
+<p>Deletes the specified keys from all configuration files.</p>
 <h4 id="edit2">edit</h4>
 <pre lang="bash"><code>npm config edit
 </code></pre>
diff --git a/deps/npm/docs/output/commands/npm-deprecate.html b/deps/npm/docs/output/commands/npm-deprecate.html
index 923448c9211..949be43d9be 100644
--- a/deps/npm/docs/output/commands/npm-deprecate.html
+++ b/deps/npm/docs/output/commands/npm-deprecate.html
@@ -145,7 +145,7 @@ npm command-line interface
 </section>
 
 <div id="_content"><h3 id="synopsis">Synopsis</h3>
-<pre lang="bash"><code>npm deprecate &lt;pkg&gt;[@&lt;version&gt;] &lt;message&gt;
+<pre lang="bash"><code>npm deprecate &lt;pkg&gt;[@&lt;version range&gt;] &lt;message&gt;
 </code></pre>
 <h3 id="description">Description</h3>
 <p>This command will update the npm registry entry for a package, providing a
@@ -154,8 +154,13 @@ deprecation warning to all who attempt to install it.</p>
 versions, so you can do something like this:</p>
 <pre lang="bash"><code>npm deprecate my-thing@"&lt; 0.2.3" "critical bug fixed in v0.2.3"
 </code></pre>
-<p>Note that you must be the package owner to deprecate something.  See the
-<code>owner</code> and <code>adduser</code> help topics.</p>
+<p>SemVer ranges passed to this command are interpreted such that they <em>do</em>
+include prerelease versions.  For example:</p>
+<pre lang="bash"><code>npm deprecate my-thing@1.x "1.x is no longer supported"
+</code></pre>
+<p>In this case, a version <code>my-thing@1.0.0-beta.0</code> will also be deprecated.</p>
+<p>You must be the package owner to deprecate something.  See the <code>owner</code> and
+<code>adduser</code> help topics.</p>
 <p>To un-deprecate a package, specify an empty string (<code>""</code>) for the <code>message</code>
 argument. Note that you must use double quotes with no space between them to
 format an empty string.</p>
diff --git a/deps/npm/docs/output/commands/npm-ls.html b/deps/npm/docs/output/commands/npm-ls.html
index 125bbb61939..1348f9c4ba6 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.2.0 /path/to/npm
+<pre lang="bash"><code>npm@7.3.0 /path/to/npm
 └─┬ init-package-json@0.0.4
   └── promzard@0.1.5
 </code></pre>
diff --git a/deps/npm/docs/output/commands/npm-run-script.html b/deps/npm/docs/output/commands/npm-run-script.html
index 8f80a761d63..57f6e6e2b65 100644
--- a/deps/npm/docs/output/commands/npm-run-script.html
+++ b/deps/npm/docs/output/commands/npm-run-script.html
@@ -181,17 +181,17 @@ provided by locally-installed dependencies can be used without the
 on Unix-like systems it is the <code>/bin/sh</code> command, on Windows it is the <code>cmd.exe</code>.
 The actual shell referred to by <code>/bin/sh</code> also depends on the system.
 You can customize the shell with the <code>script-shell</code> configuration.</p>
-<p>Scripts are run from the root of the module, regardless of what the current
-working directory is when <code>npm run</code> is called. If you want your script to
-use different behavior based on what subdirectory you’re in, you can use the
-<code>INIT_CWD</code> environment variable, which holds the full path you were in when
-you ran <code>npm run</code>.</p>
-<p><code>npm run</code> sets the <code>NODE</code> environment variable to the <code>node</code> executable with
-which <code>npm</code> is executed. Also, if the <code>--scripts-prepend-node-path</code> is passed,
-the directory within which <code>node</code> resides is added to the
-<code>PATH</code>. If <code>--scripts-prepend-node-path=auto</code> is passed (which has been the
-default in <code>npm</code> v3), this is only performed when that <code>node</code> executable is
-not found in the <code>PATH</code>.</p>
+<p>Scripts are run from the root of the package folder, regardless of what the
+current working directory is when <code>npm run</code> is called. If you want your
+script to use different behavior based on what subdirectory you’re in, you
+can use the <code>INIT_CWD</code> environment variable, which holds the full path you
+were in when you ran <code>npm run</code>.</p>
+<p><code>npm run</code> sets the <code>NODE</code> environment variable to the <code>node</code> executable
+with which <code>npm</code> is executed. Also, if the <code>--scripts-prepend-node-path</code> is
+passed, the directory within which <code>node</code> resides is added to the <code>PATH</code>.
+If <code>--scripts-prepend-node-path=auto</code> is passed (which has been the default
+in <code>npm</code> v3), this is only performed when that <code>node</code> executable is 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>
diff --git a/deps/npm/docs/output/commands/npm.html b/deps/npm/docs/output/commands/npm.html
index 03c78497612..6e9e2a618f1 100644
--- a/deps/npm/docs/output/commands/npm.html
+++ b/deps/npm/docs/output/commands/npm.html
@@ -141,14 +141,14 @@ npm command-line interface
 
 <section id="table_of_contents">
 <h2 id="table-of-contents">Table of contents</h2>
-<div id="_table_of_contents"><ul><li><a href="#synopsis">Synopsis</a></li><li><a href="#version">Version</a></li><li><a href="#description">Description</a></li><li><a href="#important">Important</a></li><li><a href="#introduction">Introduction</a></li><li><a href="#dependencies">Dependencies</a></li><li><a href="#directories">Directories</a></li><li><a href="#developer-usage">Developer Usage</a></li><ul><li><a href="#configuration">Configuration</a></li></ul><li><a href="#contributions">Contributions</a></li><li><a href="#bugs">Bugs</a></li><li><a href="#author">Author</a></li><li><a href="#see-also">See Also</a></li></ul></div>
+<div id="_table_of_contents"><ul><li><a href="#synopsis">Synopsis</a></li><li><a href="#version">Version</a></li><li><a href="#description">Description</a></li><li><a href="#important">Important</a></li><li><a href="#introduction">Introduction</a></li><li><a href="#dependencies">Dependencies</a></li><li><a href="#directories">Directories</a></li><li><a href="#developer-usage">Developer Usage</a></li><ul><li><a href="#configuration">Configuration</a></li></ul><li><a href="#contributions">Contributions</a></li><li><a href="#bugs">Bugs</a></li><li><a href="#feature-requests">Feature Requests</a></li><li><a href="#author">Author</a></li><li><a href="#see-also">See Also</a></li></ul></div>
 </section>
 
 <div id="_content"><h3 id="synopsis">Synopsis</h3>
 <pre lang="bash"><code>npm &lt;command&gt; [args]
 </code></pre>
 <h3 id="version">Version</h3>
-<p>7.2.0</p>
+<p>7.3.0</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
@@ -255,12 +255,20 @@ the contributing guidelines and check the issues list.</p>
 <p>When you find issues, please report them:</p>
 <ul>
 <li>web:
+<a href="https://github.com/npm/npm/issues">https://github.com/npm/npm/issues</a></li>
+<li>archived web:
 <a href="https://npm.community/c/bugs">https://npm.community/c/bugs</a></li>
 </ul>
-<p>Be sure to follow the template and bug reporting guidelines. You can also ask
-for help in the <a href="https://npm.community/c/support">support forum</a> if you’re
-unsure if it’s actually a bug or are having trouble coming up with a detailed
-reproduction to report.</p>
+<p>Be sure to follow the template and bug reporting guidelines.</p>
+<h3 id="feature-requests">Feature Requests</h3>
+<p>Discuss new feature ideas on our discussion forum:</p>
+<ul>
+<li><a href="https://github.com/npm/feedback">https://github.com/npm/feedback</a></li>
+</ul>
+<p>Or suggest formal RFC proposals:</p>
+<ul>
+<li><a href="https://github.com/npm/rfcs">https://github.com/npm/rfcs</a></li>
+</ul>
 <h3 id="author">Author</h3>
 <p><a href="http://blog.izs.me/">Isaac Z. Schlueter</a> ::
 <a href="https://github.com/isaacs/">isaacs</a> ::