deps: upgrade npm to 11.0.0

PR-URL: #56274 Reviewed-By: Jordan Harband <ljharb@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>

Author: npm-cli-bot

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

@@ -27,7 +27,7 @@ packages will *also* show the paths to the specified packages. For
 example, running `npm ls promzard` in npm's source tree will show:
 
 ```bash
-npm@10.9.2 /path/to/npm
+npm@11.0.0 /path/to/npm
 └─┬ init-package-json@0.0.4
  └── promzard@0.1.5
 ```
@@ -43,34 +43,6 @@ dependencies, not the physical layout of your `node_modules` folder.
 
 When run as `ll` or `la`, it shows extended information by default.
 
-### Note: Design Changes Pending
-
-The `npm ls` command's output and behavior made a _ton_ of sense when npm
-created a `node_modules` folder that naively nested every dependency. In
-such a case, the logical dependency graph and physical tree of packages on
-disk would be roughly identical.
-
-With the advent of automatic install-time deduplication of dependencies in
-npm v3, the `ls` output was modified to display the logical dependency
-graph as a tree structure, since this was more useful to most users.
-However, without using `npm ls -l`, it became impossible to show _where_ a
-package was actually installed much of the time!
-
-With the advent of automatic installation of `peerDependencies` in npm v7,
-this gets even more curious, as `peerDependencies` are logically
-"underneath" their dependents in the dependency graph, but are always
-physically at or above their location on disk.
-
-Also, in the years since npm got an `ls` command (in version 0.0.2!),
-dependency graphs have gotten much larger as a general rule. Therefore, in
-order to avoid dumping an excessive amount of content to the terminal, `npm
-ls` now only shows the _top_ level dependencies, unless `--all` is
-provided.
-
-A thorough re-examination of the use cases, intention, behavior, and output
-of this command, is currently underway. Expect significant changes to at
-least the default human-readable `npm ls` output in npm v8.
-
 ### Configuration
 
 #### `all`

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

@@ -103,6 +103,20 @@ the specified workspaces, and not on the root project.
 
 This value is not exported to the environment for child processes.
 
+#### `ignore-scripts`
+
+* Default: false
+* Type: Boolean
+
+If true, npm does not run scripts specified in package.json files.
+
+Note that commands explicitly intended to run a particular script, such as
+`npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run-script`
+will still run their intended script if `ignore-scripts` is set, but they
+will *not* run any pre- or post-scripts.
+
+
+
 ### Description
 
 For anything that's installable (that is, a package folder, tarball,

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

@@ -7,7 +7,7 @@ description: Display prefix
 ### Synopsis
 
 ```bash
-npm prefix [-g]
+npm prefix
 ```
 
 Note: This command is unaware of workspaces.

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

@@ -85,6 +85,9 @@ See [`developers`](/using-npm/developers) for full details on what's
 included in the published package, as well as details on how the package is
 built.
 
+See [`package.json`](/configuring-npm/package-json) for more info on
+what can and can't be ignored.
+
 ### Configuration
 
 #### `tag`

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

@@ -14,7 +14,7 @@ Note: This command is unaware of workspaces.
 
 ### Version
 
-10.9.2
+11.0.0
 
 ### Description
 

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

@@ -103,7 +103,7 @@ The full list is:
  - `username`
  - `_password`
  - `email`
- - `certfile` (path to certificate file)
+ - `cafile` (path to certificate authority file)
  - `keyfile` (path to key file)
 
 In order to scope these values, they must be prefixed by a URI fragment.

deps/npm/docs/content/configuring-npm/npmrc.md

@@ -324,6 +324,7 @@ Some files are always ignored by default:
  if you wish it to be published)
 * `pnpm-lock.yaml`
 * `yarn.lock`
+* `bun.lockb`
 
 Most of these ignored files can be included specifically if included in
 the `files` globs. Exceptions to this are:
@@ -334,6 +335,7 @@ the `files` globs. Exceptions to this are:
 * `package-lock.json`
 * `pnpm-lock.yaml`
 * `yarn.lock`
+* `bun.lockb`
 
 These can not be included.
 
@@ -1129,6 +1131,18 @@ Like the `os` option, you can also block architectures:
 
 The host architecture is determined by `process.arch`
 
+### libc
+
+If your code only runs or builds in certain versions of libc, you can
+specify which ones. This field only applies if `os` is `linux`.
+
+```json
+{
+ "os": "linux",
+ "libc": "glibc"
+}
+```
+
 ### devEngines
 
 The `devEngines` field aids engineers working on a codebase to all be using the same tooling.

deps/npm/docs/content/configuring-npm/package-json.md

@@ -1833,9 +1833,9 @@ When set to `dev` or `development`, this is an alias for `--include=dev`.
 * Default: null
 * Type: null or String
 * DEPRECATED: `key` and `cert` are no longer used for most registry
- operations. Use registry scoped `keyfile` and `certfile` instead. Example:
+ operations. Use registry scoped `keyfile` and `cafile` instead. Example:
  //other-registry.tld/:keyfile=/path/to/key.pem
- //other-registry.tld/:certfile=/path/to/cert.crt
+ //other-registry.tld/:cafile=/path/to/cert.crt
 
 A client certificate to pass when accessing the registry. Values should be
 in PEM format (Windows calls it "Base-64 encoded X.509 (.CER)") with
@@ -1846,8 +1846,8 @@ cert="-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----"
 ```
 
 It is _not_ the path to a certificate file, though you can set a
-registry-scoped "certfile" path like
-"//other-registry.tld/:certfile=/path/to/cert.pem".
+registry-scoped "cafile" path like
+"//other-registry.tld/:cafile=/path/to/cert.pem".
 
 
 
@@ -1938,9 +1938,9 @@ Alias for `--init-version`
 * Default: null
 * Type: null or String
 * DEPRECATED: `key` and `cert` are no longer used for most registry
- operations. Use registry scoped `keyfile` and `certfile` instead. Example:
+ operations. Use registry scoped `keyfile` and `cafile` instead. Example:
  //other-registry.tld/:keyfile=/path/to/key.pem
- //other-registry.tld/:certfile=/path/to/cert.crt
+ //other-registry.tld/:cafile=/path/to/cert.crt
 
 A client key to pass when accessing the registry. Values should be in PEM
 format with newlines replaced by the string "\n". For example:

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

@@ -112,8 +112,8 @@ as `.gitignore` files:
 * You can end patterns with a forward slash `/` to specify a directory.
 * You can negate a pattern by starting it with an exclamation point `!`.
 
-By default, the following paths and files are ignored, so there's no
-need to add them to `.npmignore` explicitly:
+By default, some paths and files are ignored, so there's no
+need to add them to `.npmignore` explicitly. Some examples are:
 
 * `.*.swp`
 * `._*`
@@ -148,6 +148,9 @@ property of `package.json`, which is an array of file or directory names
 that should be included in your package. Sometimes manually picking
 which items to allow is easier to manage than building a block list.
 
+See [`package.json`](/configuring-npm/package-json) for more info on
+what can and can't be ignored.
+
 #### Testing whether your `.npmignore` or `files` config works
 
 If you want to double check that your package will include only the files