deps: upgrade npm to 7.4.2

PR-URL: #36953 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
nodejs · Jan 21, 2021 · 6f773fb · 6f773fb
1 parent 832cd01
commit 6f773fb
Show file tree

Hide file tree

Showing 93 changed files with 3,736 additions and 2,422 deletions.
diff --git a/deps/npm/AUTHORS b/deps/npm/AUTHORS
@@ -746,3 +746,4 @@ fuhao.xu <[email protected]>
 marsonya <[email protected]>
 Jeff Griffiths <[email protected]>
 Michael Garvin <[email protected]>
+Gar <[email protected]>
diff --git a/deps/npm/CHANGELOG.md b/deps/npm/CHANGELOG.md
@@ -1,3 +1,78 @@
+## v7.4.2 (2021-01-15)
+
+### DEPENDENCIES
+
+* [`e5ce6bbba`](https://github.com/npm/cli/commit/e5ce6bbbad82b85c8e74a4558503513e4f337476)
+  * `@npmcli/[email protected]`
+    * fix creating missing dirs when using --prefix and --global
+    * fix omit types of deps in global installs
+    * fix prioritizing npm-shrinkwrap.json over package-lock.json
+    * better cache system for packuments
+    * improves audit performance
+
+## v7.4.1 (2021-01-14)
+
+### BUG FIXES
+
+* [`23df96d33`](https://github.com/npm/cli/commit/23df96d3394ba0b69a37f416d7f0c26bb9354975)
+  [#2486](https://github.com/npm/cli/issues/2486)
+  npm link no longer deletes entire project when global prefix is a symlink
+  ([@nlf](https://github.com/nlf))
+
+### DOCUMENTATION
+
+* [`7dd0dfc59`](https://github.com/npm/cli/commit/7dd0dfc59c861e7d3e30a86a8e6db10872fc6b44)
+  [#2459](https://github.com/npm/cli/issues/2459)
+  fix(docs): clean up `npm start` docs
+  ([@wraithgar](https://github.com/wraithgar))
+* [`307b3bd9f`](https://github.com/npm/cli/commit/307b3bd9f90e96fcc8805a1d5ddec80787a3d3a7)
+  [#2460](https://github.com/npm/cli/issues/2460)
+  fix(docs): clean up `npm stop` docs
+  ([@wraithgar](https://github.com/wraithgar))
+* [`23f01b739`](https://github.com/npm/cli/commit/23f01b739d7a01a7dc3672322e14eb76ff33d712)
+  [#2462](https://github.com/npm/cli/issues/2462)
+  fix(docs): clean up `npm test` docs
+  ([@wraithgar](https://github.com/wraithgar))
+* [`4b43656fc`](https://github.com/npm/cli/commit/4b43656fc608783a29ccf8495dc305459abc5cc7)
+  [#2463](https://github.com/npm/cli/issues/2463)
+  fix(docs): clean up `npm prefix` docs
+  ([@wraithgar](https://github.com/wraithgar))
+* [`1135539ba`](https://github.com/npm/cli/commit/1135539bac9f98bb1a5d5ed05227a8ecd19493d3)
+  [`a07bb8e69`](https://github.com/npm/cli/commit/a07bb8e692a85b55d51850534c09fa58224c2285)
+  [`9b55b798e`](https://github.com/npm/cli/commit/9b55b798ed8f2b9be7b3199a1bfc23b1cd89c4cd)
+  [`cd5eeaaa0`](https://github.com/npm/cli/commit/cd5eeaaa08eabb505b65747a428c3c59159663dc)
+  [`6df69ce10`](https://github.com/npm/cli/commit/6df69ce107912f8429665eb851825d2acebc8575)
+  [`dc6b2a8b0`](https://github.com/npm/cli/commit/dc6b2a8b032d118be3566ce0fa7c67c171c8d2cb)
+  [`a3c127446`](https://github.com/npm/cli/commit/a3c1274460e16d1edbdca6a0cee86ef313fdd961)
+  [#2464](https://github.com/npm/cli/issues/2464)
+  fix(docs): clean up `npm uninstall` docs
+  ([@wraithgar](https://github.com/wraithgar))
+* [`cfdcf32fd`](https://github.com/npm/cli/commit/cfdcf32fd7628501712b8cad4a541c6b8e7b66bc)
+  [#2474](https://github.com/npm/cli/issues/2474)
+  fix(docs): clean up `npm unpublish` docs
+  ([@wraithgar](https://github.com/wraithgar))
+* [`acd5b062a`](https://github.com/npm/cli/commit/acd5b062a811fcd98849df908ce26855823ca671)
+  [#2475](https://github.com/npm/cli/issues/2475)
+  fix(docs): update `package-lock.json` docs
+  ([@isaacs](https://github.com/isaacs))
+* [`b0b0edf6d`](https://github.com/npm/cli/commit/b0b0edf6de1678de7f4a000700c88daa5f7194ef)
+  [#2482](https://github.com/npm/cli/issues/2482)
+  fix(docs): clean up `npm token` docs
+  ([@wraithgar](https://github.com/wraithgar))
+* [`35559201a`](https://github.com/npm/cli/commit/35559201a4a0a5b111ce58d6824e5b4030eb4496)
+  [#2487](https://github.com/npm/cli/issues/2487)
+  fix(docs): clean up `npm search` docs
+  ([@wraithgar](https://github.com/wraithgar))
+
+### DEPENDENCIES
+
+* [`ea8c02169`](https://github.com/npm/cli/commit/ea8c02169cfbf0484d67db7c0e7a6ec8aecb7210)
+  `@npmcli/[email protected]`
+* [`fb6f2c313`](https://github.com/npm/cli/commit/fb6f2c313d1d9770cc7d02a3900c7945df3cb661)
+  `[email protected]`
+* [`c549b7657`](https://github.com/npm/cli/commit/c549b76573b1835a63e1e5898e9c16860079d84e)
+  `[email protected]`
+
 ## v7.4.0 (2021-01-07)
 
 ### FEATURES

diff --git a/deps/npm/docs/content/commands/npm-audit.md b/deps/npm/docs/content/commands/npm-audit.md
@@ -190,5 +190,4 @@ $ npm audit --audit-level=moderate
 ### See Also
 
 * [npm install](/commands/npm-install)
-* [package-locks](/configuring-npm/package-locks)
 * [config](/using-npm/config)
diff --git a/deps/npm/docs/content/commands/npm-ci.md b/deps/npm/docs/content/commands/npm-ci.md
@@ -68,4 +68,4 @@ cache:
 ### See Also
 
 * [npm install](/commands/npm-install)
-* [package-locks](/configuring-npm/package-locks)
+* [package-lock.json](/configuring-npm/package-lock-json)
diff --git a/deps/npm/docs/content/commands/npm-prefix.md b/deps/npm/docs/content/commands/npm-prefix.md
@@ -12,13 +12,25 @@ npm prefix [-g]
 
 ### Description
 
-Print the local prefix to standard out. This is the closest parent directory
+Print the local prefix to standard output. This is the closest parent directory
 to contain a `package.json` file or `node_modules` directory, unless `-g` is
 also specified.
 
 If `-g` is specified, this will be the value of the global prefix. See
 [`npm config`](/commands/npm-config) for more detail.
 
+### Example
+
+```bash
+npm prefix
+/usr/local/projects/foo
+```
+
+```bash
+npm prefix -g
+/usr/local
+```
+
 ### See Also
 
 * [npm root](/commands/npm-root)

diff --git a/deps/npm/docs/content/commands/npm-search.md b/deps/npm/docs/content/commands/npm-search.md
@@ -16,35 +16,42 @@ aliases: s, se, find
 
 Search the registry for packages matching the search terms. `npm search`
 performs a linear, incremental, lexically-ordered search through package
-metadata for all files in the registry. If color is enabled, it will further
-highlight the matches in the results.
+metadata for all files in the registry. If your terminal has color
+support, it will further highlight the matches in the results.  This can
+be disabled with the config item `color`
 
-Additionally, using the `--searchopts` and `--searchexclude` options paired with
-more search terms will respectively include and exclude further patterns. The
-main difference between `--searchopts` and the standard search terms is that the
-former does not highlight results in the output and can be used for more
-fine-grained filtering. Additionally, both of these can be added to `.npmrc` for
-default search filtering behavior.
+Additionally, using the `--searchopts` and `--searchexclude` options
+paired with more search terms will include and exclude further patterns.
+The main difference between `--searchopts` and the standard search terms
+is that the former does not highlight results in the output and you can
+use them more fine-grained filtering. Additionally, you can add both of
+these to your config to change default search filtering behavior.
 
 Search also allows targeting of maintainers in search results, by prefixing
 their npm username with `=`.
 
-If a term starts with `/`, then it's interpreted as a regular expression and
-supports standard JavaScript RegExp syntax. A trailing `/` will be ignored in
-this case. (Note that many regular expression characters must be escaped or
-quoted in most shells.)
-
-### A Note on caching
+If a term starts with `/`, then it's interpreted as a regular expression
+and supports standard JavaScript RegExp syntax. In this case search will
+ignore a trailing `/` .  (Note you must escape or quote many regular
+expression characters in most shells.)
 
 ### Configuration
 
+All of the following can be defined in a `.npmrc` file, or passed as
+parameters to the cli prefixed with `--` (e.g. `--json`)
+
 #### description
 
 * Default: true
 * Type: Boolean
 
-Used as `--no-description`, disables search matching in package descriptions and
-suppresses display of that field in results.
+#### color
+
+ * Default: true
+ * Type: Boolean
+
+Used as `--no-color`, disables color highlighting of matches in the
+results.
 
 #### json
 
@@ -66,9 +73,9 @@ Output search results as lines with tab-separated columns.
 * Type: Boolean
 
 Display full package descriptions and other long text across multiple
-lines. When disabled (default) search results are truncated to fit
-neatly on a single line. Modules with extremely long names will
-fall on multiple lines.
+lines. When disabled (which is the default) the output will
+truncate search results to fit neatly on a single line. Modules with
+extremely long names will fall on multiple lines.
 
 #### searchopts
 
@@ -84,27 +91,43 @@ Space-separated options that are always passed to search.
 
 Space-separated options that limit the results from search.
 
-#### searchstaleness
-
-* Default: 900 (15 minutes)
-* Type: Number
-
-The age of the cache, in seconds, before another registry request is made.
-
 #### registry
 
  * Default: https://registry.npmjs.org/
  * Type: url
 
-Search the specified registry for modules. If you have configured npm to point
-to a different default registry, such as your internal private module
-repository, `npm search` will default to that registry when searching. Pass a
-different registry url such as the default above in order to override this
-setting.
+Search the specified registry for modules. If you have configured npm to
+point to a different default registry (such as your internal private
+module repository), `npm search` will also default to that registry when
+searching.
+
+### A note on caching
+
+The npm cli caches search results with the same terms and options
+locally in its cache. You can use the following to change how and when
+the cli uses this cache. See [`npm cache`](/commands/npm-cache) for more
+on how the cache works.
+
+#### prefer-online
+
+Forced staleness checks for cached searches, making the cli look for
+updates immediately even for fresh search results.
+
+#### prefer-offline
+
+Bypasses staleness checks for cached.  Missing data will still be
+requested from the server. To force full offline mode, use `offline`.
+
+#### offline
+
+Forces full offline mode. Any searches not locally cached will result in
+an error.
 
 ### See Also
 
 * [npm registry](/using-npm/registry)
 * [npm config](/commands/npm-config)
 * [npmrc](/configuring-npm/npmrc)
 * [npm view](/commands/npm-view)
+* [npm cache](/commands/npm-cache)
+* https://npm.im/npm-registry-fetch
diff --git a/deps/npm/docs/content/commands/npm-shrinkwrap.md b/deps/npm/docs/content/commands/npm-shrinkwrap.md
@@ -13,18 +13,18 @@ npm shrinkwrap
 ### Description
 
 This command repurposes `package-lock.json` into a publishable
-`npm-shrinkwrap.json` or simply creates a new one. The file created and updated
-by this command will then take precedence over any other existing or future
-`package-lock.json` files. For a detailed explanation of the design and purpose
-of package locks in npm, see [package-locks](/configuring-npm/package-locks).
+`npm-shrinkwrap.json` or simply creates a new one. The file created and
+updated by this command will then take precedence over any other existing
+or future `package-lock.json` files. For a detailed explanation of the
+design and purpose of package locks in npm, see
+[package-lock-json](/configuring-npm/package-lock-json).
 
 ### See Also
 
 * [npm install](/commands/npm-install)
 * [npm run-script](/commands/npm-run-script)
 * [npm scripts](/using-npm/scripts)
-* [package.js](/configuring-npm/package-json)
-* [package-locks](/configuring-npm/package-locks)
+* [package.json](/configuring-npm/package-json)
 * [package-lock.json](/configuring-npm/package-lock-json)
-* [shrinkwrap.json](/configuring-npm/shrinkwrap-json)
+* [npm-shrinkwrap.json](/configuring-npm/npm-shrinkwrap-json)
 * [npm ls](/commands/npm-ls)
diff --git a/deps/npm/docs/content/commands/npm-start.md b/deps/npm/docs/content/commands/npm-start.md
@@ -12,13 +12,39 @@ npm start [-- <args>]
 
 ### Description
 
-This runs an arbitrary command specified in the package's `"start"` property of
-its `"scripts"` object. If no `"start"` property is specified on the
-`"scripts"` object, it will run `node server.js`.
+This runs a predefined command specified in the `"start"` property of
+a package's `"scripts"` object.
+
+If the `"scripts"` object does not define a  `"start"` property, npm
+will run `node server.js`.
+
+Note that this is different from the default node behavior of running
+the file specified in a package's `"main"` attribute when evoking with
+`node .`
 
 As of [`[email protected]`](https://blog.npmjs.org/post/98131109725/npm-2-0-0), you can
 use custom arguments when executing scripts. Refer to [`npm run-script`](/commands/npm-run-script) for more details.
 
+### Example
+
+```json
+{
+  "scripts": {
+    "start": "node foo.js"
+  }
+}
+```
+
+```bash
+npm start
+
+> [email protected] start
+> node foo.js
+
+(foo.js output would be here)
+
+```
+
 ### See Also
 
 * [npm run-script](/commands/npm-run-script)

diff --git a/deps/npm/docs/content/commands/npm-stop.md b/deps/npm/docs/content/commands/npm-stop.md
@@ -12,7 +12,31 @@ npm stop [-- <args>]
 
 ### Description
 
-This runs a package's "stop" script, if one was provided.
+This runs a predefined command specified in the "stop" property of a
+package's "scripts" object.
+
+Unlike with [npm start](/commands/npm-start), there is no default script
+that will run if the `"stop"` property is not defined.
+
+### Example
+
+```json
+{
+  "scripts": {
+    "stop": "node bar.js"
+  }
+}
+```
+
+```bash
+npm stop
+
+> [email protected] stop
+> node bar.js
+
+(bar.js output would be here)
+
+```
 
 ### See Also
 

diff --git a/deps/npm/docs/content/commands/npm-test.md b/deps/npm/docs/content/commands/npm-test.md
@@ -14,7 +14,28 @@ aliases: t, tst
 
 ### Description
 
-This runs a package's "test" script, if one was provided.
+This runs a predefined command specified in the `"test"` property of
+a package's `"scripts"` object.
+
+### Example
+
+```json
+{
+  "scripts": {
+    "test": "node test.js"
+  }
+}
+```
+
+```bash
+npm test
+> [email protected] test
+> node test.js
+
+(test.js output would be here)
+```
+
+
 
 ### See Also