deps: upgrade npm to 7.3.0

PR-URL: #36572
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>

Author: ruyadorno

deps/npm/.eslintrc.json

@@ -67,6 +67,13 @@
     "key-spacing": ["error", { "beforeColon": false, "afterColon": true }],
     "keyword-spacing": ["error", { "before": true, "after": true }],
     "lines-between-class-members": ["error", "always", { "exceptAfterSingleLine": true }],
+    "max-len": ["error", 80, {
+      "ignoreUrls": true,
+      "ignoreComments": false,
+      "ignoreRegExpLiterals": true,
+      "ignoreStrings": true,
+      "ignoreTemplateLiterals": true
+    }],
     "new-cap": ["error", { "newIsCap": true, "capIsNew": false, "properties": true }],
     "new-parens": "error",
     "no-array-constructor": "error",

deps/npm/AUTHORS

@@ -739,3 +739,5 @@ kai zhu <[email protected]>
 Alex Woollam <[email protected]>
 Daniel Fischer <[email protected]>
 Yash-Singh1 <[email protected]>
+Edu93Jer <[email protected]>
+Tieg Zaharia <[email protected]>

deps/npm/CHANGELOG.md

@@ -1,3 +1,75 @@
+## 7.3.0 (2020-12-18)
+
+### FEATURES
+
+* [`a9b8bf263`](https://github.com/npm/cli/commit/a9b8bf2634c627fbb16ca3a6bb2c2f1058c3e586)
+  [#2362](https://github.com/npm/cli/issues/2362)
+  Support multiple set/get/deletes in npm config
+  ([@isaacs](https://github.com/isaacs))
+
+### BUG FIXES
+
+* [`9eef63849`](https://github.com/npm/cli/commit/9eef638499c88689acb00d812c10f0407cb95c08)
+  Pass full set of options to login helper functions.
+  This fixes `npm login --no-strict-ssl`, as well as a host of other
+  options that one might want to set while logging in.
+  Reported by: [@toddself](https://github.com/toddself)
+  ([@isaacs](https://github.com/isaacs))
+* [`628a554bc`](https://github.com/npm/cli/commit/628a554bc113e4e115d34778bfe8a77cfad1d933)
+  [#2358](https://github.com/npm/cli/issues/2358)
+  fix doctor test to work correctly for node pre-release versions
+  ([@nlf](https://github.com/nlf))
+* [`be4a0900b`](https://github.com/npm/cli/commit/be4a0900b14b2c6315bf62bed8f5affb648215ae)
+  [#2360](https://github.com/npm/cli/issues/2360)
+  raise an error early if publishing without login, registry
+  ([@isaacs](https://github.com/isaacs))
+* [`44d433105`](https://github.com/npm/cli/commit/44d4331058c53909ada62470b23b2185102b2128)
+  [#2366](https://github.com/npm/cli/issues/2366)
+  Include prerelease versions when deprecating
+  ([@tiegz](https://github.com/tiegz))
+* [`cba3341da`](https://github.com/npm/cli/commit/cba3341dae4c92541049dc976e82e2ba19566e95)
+  [#2373](https://github.com/npm/cli/issues/2373)
+  npm profile refactor
+  ([@ruyadorno](https://github.com/ruyadorno))
+* [`7539504e3`](https://github.com/npm/cli/commit/7539504e3abdec28039a7798e5ccb745b536cb6e)
+  [#2382](https://github.com/npm/cli/issues/2382)
+  remove the metrics sender
+  ([@nlf](https://github.com/nlf))
+
+### DOCS
+
+* [`b98569a8c`](https://github.com/npm/cli/commit/b98569a8ca28dbd611fe84492aee996e2e567b55)
+  add note about `INIT_CWD` to run-script doc
+* [`292929279`](https://github.com/npm/cli/commit/292929279854a06ca60ff737b574cbd6503ec5db)
+  [#2368](https://github.com/npm/cli/issues/2368)
+  Revert bug-reporting links to GH.
+  Re: <https://blog.npmjs.org/post/188841555980/updates-to-community-docs-more>
+  ([@tiegz](https://github.com/tiegz))
+* [`f4560626f`](https://github.com/npm/cli/commit/f4560626f09dba4889d752f7f739aa5a5f3da741)
+  update `ISSUE_TEMPLATE` with modern links
+  ([@isaacs](https://github.com/isaacs))
+* [`bc1c567ed`](https://github.com/npm/cli/commit/bc1c567ed3d853ed4f01d33a800eb453956de6ef)
+  update npm command doc feature request links
+  ([@isaacs](https://github.com/isaacs))
+* [`0ad958fe1`](https://github.com/npm/cli/commit/0ad958fe1cb811699caca235f361c8328baac8c4)
+  [#2381](https://github.com/npm/cli/issues/2381)
+  (docs,test): assorted typo fixes
+  ([@XhmikosR](https://github.com/XhmikosR))
+
+### TESTING
+
+* [`a92d310b7`](https://github.com/npm/cli/commit/a92d310b7e9e4c48b08f52785c2e3a6d52a82ad7)
+  [#2361](https://github.com/npm/cli/issues/2361)
+  Add max-len to lint rules
+  ([@Edu93Jer](https://github.com/Edu93Jer))
+
+### DEPENDENCIES
+
+* [`4fc2f3e05`](https://github.com/npm/cli/commit/4fc2f3e05b600aa64fe5eb6b8b77bc070e5a9403)
+  [#2300](https://github.com/npm/cli/issues/2300)
+  `@npmcli/[email protected]`:
+    * Support setting email without username/password
+
 ## 7.2.0 (2020-12-15)
 
 ### FEATURES
@@ -977,7 +1049,7 @@
     * fix package.json dependencies order
 * [`49b2bf5a7`](https://github.com/npm/cli/commit/49b2bf5a798b49d52166744088a80b8a39ccaeb6)
   `@npmcli/[email protected]`
-    * fix unkown envs to be passed through
+    * fix unknown envs to be passed through
     * fix setting correct globalPrefix on load
 * [`f9aac351d`](https://github.com/npm/cli/commit/f9aac351dd36a19d14e1f951a2e8e20b41545822)
   `[email protected]`

deps/npm/Makefile

@@ -88,13 +88,13 @@ prune:
 	@[[ "$(shell git status -s)" != "" ]] && echo "ERR: found unpruned files" && exit 1 || echo "git status is clean"
 
 
-publish: gitclean ls-ok link test docs-clean docs prune
+publish: gitclean ls-ok link test docs prune
 	@git push origin :v$(shell node bin/npm-cli.js --no-timing -v) 2>&1 || true
 	git push origin $(BRANCH) &&\
 	git push origin --tags &&\
 	node bin/npm-cli.js publish --tag=$(PUBLISHTAG)
 
-release: gitclean ls-ok docs-clean docs prune
+release: gitclean ls-ok docs prune
 	@bash scripts/release.sh
 
 .PHONY: all latest install dev link docs clean uninstall test man docs-clean docsclean release ls-ok dev-deps prune

deps/npm/README.md

@@ -150,6 +150,8 @@ you should [read this](https://docs.npmjs.com/misc/developers).
 When you find issues, please report them:
 
 * web:
+  <https://github.com/npm/npm/issues>
+* archived web:
   <https://npm.community/c/bugs>
 
 Be sure to include *all* of the output from the npm command that didn't work

deps/npm/docs/content/commands/npm-config.md

@@ -7,15 +7,15 @@ description: Manage the npm configuration files
 ### Synopsis
 
 ```bash
-npm config set <key> <value> [-g|--global]
-npm config get <key>
-npm config delete <key>
-npm config list [-l] [--json]
+npm config set <key>=<value> [<key>=<value> ...]
+npm config get [<key> [<key> ...]]
+npm config delete <key> [<key> ...]
+npm config list [--json]
 npm config edit
-npm get <key>
-npm set <key> <value> [-g|--global]
+npm set <key>=<value> [<key>=<value> ...]
+npm get [<key> [<key> ...]]
 
-aliases: c
+alias: c
 ```
 
 ### Description
@@ -39,20 +39,31 @@ Config supports the following sub-commands:
 #### set
 
 ```bash
-npm config set key value
+npm config set key=value [key=value...]
+npm set key=value [key=value...]
 ```
 
-Sets the config key to the value.
+Sets each of the config keys to the value provided.
 
-If value is omitted, then it sets it to "true".
+If value is omitted, then it sets it to an empty string.
+
+Note: for backwards compatibility, `npm config set key value` is supported
+as an alias for `npm config set key=value`.
 
 #### get
 
 ```bash
-npm config get key
+npm config get [key ...]
+npm get [key ...]
 ```
 
-Echo the config value to stdout.
+Echo the config value(s) to stdout.
+
+If multiple keys are provided, then the values will be prefixed with the
+key names.
+
+If no keys are provided, then this command behaves the same as `npm config
+list`.
 
 #### list
 
@@ -66,10 +77,10 @@ to show the settings in json format.
 #### delete
 
 ```bash
-npm config delete key
+npm config delete key [key ...]
 ```
 
-Deletes the key from all configuration files.
+Deletes the specified keys from all configuration files.
 
 #### edit
 

deps/npm/docs/content/commands/npm-deprecate.md

@@ -7,7 +7,7 @@ description: Deprecate a version of a package
 ### Synopsis
 
 ```bash
-npm deprecate <pkg>[@<version>] <message>
+npm deprecate <pkg>[@<version range>] <message>
 ```
 
 ### Description
@@ -22,8 +22,17 @@ versions, so you can do something like this:
 npm deprecate my-thing@"< 0.2.3" "critical bug fixed in v0.2.3"
 ```
 
-Note that you must be the package owner to deprecate something.  See the
-`owner` and `adduser` help topics.
+SemVer ranges passed to this command are interpreted such that they *do*
+include prerelease versions.  For example:
+
+```bash
+npm deprecate [email protected] "1.x is no longer supported"
+```
+
+In this case, a version `[email protected]` will also be deprecated.
+
+You must be the package owner to deprecate something.  See the `owner` and
+`adduser` help topics.
 
 To un-deprecate a package, specify an empty string (`""`) for the `message` 
 argument. Note that you must use double quotes with no space between them to 

deps/npm/docs/content/commands/npm-run-script.md

@@ -60,18 +60,18 @@ on Unix-like systems it is the `/bin/sh` command, on Windows it is the `cmd.exe`
 The actual shell referred to by `/bin/sh` also depends on the system.
 You can customize the shell with the `script-shell` configuration.
 
-Scripts are run from the root of the module, regardless of what the current
-working directory is when `npm run` is called. If you want your script to
-use different behavior based on what subdirectory you're in, you can use the
-`INIT_CWD` environment variable, which holds the full path you were in when
-you ran `npm run`.
-
-`npm run` sets the `NODE` environment variable to the `node` executable with
-which `npm` is executed. Also, if the `--scripts-prepend-node-path` is passed,
-the directory within which `node` resides is added to the
-`PATH`. If `--scripts-prepend-node-path=auto` is passed (which has been the
-default in `npm` v3), this is only performed when that `node` executable is
-not found in the `PATH`.
+Scripts are run from the root of the package folder, regardless of what the
+current working directory is when `npm run` is called. If you want your
+script to use different behavior based on what subdirectory you're in, you
+can use the `INIT_CWD` environment variable, which holds the full path you
+were in when you ran `npm run`.
+
+`npm run` sets the `NODE` environment variable to the `node` executable
+with which `npm` is executed. Also, if the `--scripts-prepend-node-path` is
+passed, the directory within which `node` resides is added to the `PATH`.
+If `--scripts-prepend-node-path=auto` is passed (which has been the default
+in `npm` v3), this is only performed when that `node` executable is not
+found in the `PATH`.
 
 If you try to run a script without having a `node_modules` directory and it fails,
 you will be given a warning to run `npm install`, just in case you've forgotten.

deps/npm/docs/content/commands/npm.md

@@ -143,12 +143,21 @@ the contributing guidelines and check the issues list.
 When you find issues, please report them:
 
 * web:
+  <https://github.com/npm/npm/issues>
+* archived web:
   <https://npm.community/c/bugs>
 
-Be sure to follow the template and bug reporting guidelines. You can also ask
-for help in the [support forum](https://npm.community/c/support) if you're
-unsure if it's actually a bug or are having trouble coming up with a detailed
-reproduction to report.
+Be sure to follow the template and bug reporting guidelines.
+
+### Feature Requests
+
+Discuss new feature ideas on our discussion forum:
+
+* <https://github.com/npm/feedback>
+
+Or suggest formal RFC proposals:
+
+* <https://github.com/npm/rfcs>
 
 ### Author
 

deps/npm/docs/content/using-npm/config.md

@@ -744,13 +744,6 @@ Commit message which is used by `npm version` when creating version commit.
 
 Any "%s" in the message will be replaced with the version number.
 
-#### metrics-registry
-
-* Default: The value of  `registry` (which defaults to "https://registry.npmjs.org/")
-* Type: String
-
-The registry you want to send cli metrics to if `send-metrics` is true.
-
 #### node-options
 
 * Default: null
@@ -1089,16 +1082,6 @@ searches.
 The age of the cache, in seconds, before another registry request is made if
 using legacy search endpoint.
 
-#### send-metrics
-
-* Default: false
-* Type: Boolean
-
-If true, success/failure metrics will be reported to the registry stored in
-`metrics-registry`.  These requests contain the number of successful and
-failing runs of the npm CLI and the time period over which those counts were
-gathered. No identifying information is included in these requests.
-
 #### shell
 
 * Default: SHELL environment variable, or "bash" on Posix, or "cmd" on

deps/npm/docs/content/using-npm/scripts.md

@@ -24,7 +24,7 @@ To create "pre" or "post" scripts for any scripts defined in the `"scripts"` sec
 
 ### Life Cycle Scripts
 
-There are some special life cycle scripts that happen only in certain situations. These scripts happen in addtion to the "pre" and "post" script.
+There are some special life cycle scripts that happen only in certain situations. These scripts happen in addition to the "pre" and "post" script.
 * `prepare`, `prepublish`, `prepublishOnly`, `prepack`, `postpack`
 
 **prepare** (since `[email protected]`)

deps/npm/docs/output/commands/npm-config.html

@@ -145,15 +145,15 @@ <h2 id="table-of-contents">Table of contents</h2>
 </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 @@ <h3 id="description">Description</h3>
 <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>