deps: upgrade npm to 8.19.3

PR-URL: #45322
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>

Author: npm-cli-bot

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

@@ -6,10 +6,6 @@ description: Set access level on published packages
 
 ### Synopsis
 
-<!-- AUTOGENERATED USAGE DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/access.js -->
-
 ```bash
 npm access public [<package>]
 npm access restricted [<package>]
@@ -22,11 +18,6 @@ npm access ls-collaborators [<package> [<user>]]
 npm access edit [<package>]
 ```
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/access.js -->
-
-<!-- AUTOGENERATED USAGE DESCRIPTIONS END -->
-
 ### Description
 
 Used to set access controls on private packages.
@@ -88,19 +79,13 @@ Management of teams and team memberships is done with the `npm team` command.
 
 ### Configuration
 
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
 #### `registry`
 
 * Default: "https://registry.npmjs.org/"
 * Type: URL
 
 The base URL of the npm registry.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `otp`
 
 * Default: null
@@ -112,11 +97,6 @@ when publishing or changing package permissions with `npm access`.
 If not set, and a registry response fails with a challenge for a one-time
 password, npm will prompt on the command line for one.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
-
 ### See Also
 
 * [`libnpmaccess`](https://npm.im/libnpmaccess)

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

@@ -6,21 +6,12 @@ description: Add a registry user account
 
 ### Synopsis
 
-<!-- AUTOGENERATED USAGE DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/adduser.js -->
-
 ```bash
 npm adduser
 
 aliases: login, add-user
 ```
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/adduser.js -->
-
-<!-- AUTOGENERATED USAGE DESCRIPTIONS END -->
-
 Note: This command is unaware of workspaces.
 
 ### Description
@@ -44,19 +35,13 @@ your existing record.
 
 ### Configuration
 
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
 #### `registry`
 
 * Default: "https://registry.npmjs.org/"
 * Type: URL
 
 The base URL of the npm registry.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `scope`
 
 * Default: the scope of the current project, if any, or ""
@@ -87,9 +72,6 @@ npm init --scope=@foo --yes
 ```
 
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `auth-type`
 
 * Default: "legacy"
@@ -100,11 +82,6 @@ removed in a future version.
 
 What authentication strategy to use with `login`.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
-
 ### See Also
 
 * [npm registry](/using-npm/registry)

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

@@ -6,19 +6,10 @@ description: Run a security audit
 
 ### Synopsis
 
-<!-- AUTOGENERATED USAGE DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/audit.js -->
-
 ```bash
 npm audit [fix|signatures]
 ```
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/audit.js -->
-
-<!-- AUTOGENERATED USAGE DESCRIPTIONS END -->
-
 ### Description
 
 The audit command submits a description of the dependencies configured in
@@ -247,9 +238,6 @@ $ npm audit --audit-level=moderate
 
 ### Configuration
 
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
 #### `audit-level`
 
 * Default: null
@@ -258,9 +246,6 @@ $ npm audit --audit-level=moderate
 The minimum level of vulnerability for `npm audit` to exit with a non-zero
 exit code.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `dry-run`
 
 * Default: false
@@ -274,9 +259,6 @@ commands that modify your local installation, eg, `install`, `update`,
 Note: This is NOT honored by other network related commands, eg `dist-tags`,
 `owner`, etc.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `force`
 
 * Default: false
@@ -303,9 +285,6 @@ mistakes, unnecessary performance degradation, and malicious input.
 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!
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `json`
 
 * Default: false
@@ -318,9 +297,6 @@ Whether or not to output JSON data, rather than the normal output.
 
 Not supported by all npm commands.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `package-lock-only`
 
 * Default: false
@@ -335,9 +311,6 @@ instead of checking `node_modules` and downloading dependencies.
 For `list` this means the output will be based on the tree described by the
 `package-lock.json`, rather than the contents of `node_modules`.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `omit`
 
 * Default: 'dev' if the `NODE_ENV` environment variable is set to
@@ -356,9 +329,6 @@ it will be included.
 If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment
 variable will be set to `'production'` for all lifecycle scripts.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `foreground-scripts`
 
 * Default: false
@@ -371,9 +341,6 @@ input, output, and error with the main npm process.
 Note that this will generally make installs run slower, and be much noisier,
 but can be useful for debugging.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `ignore-scripts`
 
 * Default: false
@@ -386,9 +353,6 @@ Note that commands explicitly intended to run a particular script, such as
 will still run their intended script if `ignore-scripts` is set, but they
 will *not* run any pre- or post-scripts.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `workspace`
 
 * Default:
@@ -411,9 +375,6 @@ brand new workspace within the project.
 
 This value is not exported to the environment for child processes.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `workspaces`
 
 * Default: null
@@ -432,9 +393,6 @@ _unless_ one or more workspaces are specified in the `workspace` config.
 
 This value is not exported to the environment for child processes.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `include-workspace-root`
 
 * Default: false
@@ -448,9 +406,6 @@ the specified workspaces, and not on the root project.
 
 This value is not exported to the environment for child processes.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `install-links`
 
 * Default: false
@@ -460,11 +415,6 @@ When set file: protocol dependencies that exist outside of the project root
 will be packed and installed as regular dependencies instead of creating a
 symlink. This option has no effect on workspaces.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
-
 ### See Also
 
 * [npm install](/commands/npm-install)

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

@@ -6,19 +6,10 @@ description: Display npm bin folder
 
 ### Synopsis
 
-<!-- AUTOGENERATED USAGE DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/bin.js -->
-
 ```bash
 npm bin
 ```
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/bin.js -->
-
-<!-- AUTOGENERATED USAGE DESCRIPTIONS END -->
-
 Note: This command is unaware of workspaces.
 
 ### Description
@@ -27,9 +18,6 @@ Print the folder where npm will install executables.
 
 ### Configuration
 
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
 #### `global`
 
 * Default: false
@@ -44,11 +32,6 @@ folder instead of the current working directory. See
 * bin files are linked to `{prefix}/bin`
 * man pages are linked to `{prefix}/share/man`
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
-
 ### See Also
 
 * [npm prefix](/commands/npm-prefix)

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

@@ -6,21 +6,12 @@ description: Report bugs for a package in a web browser
 
 ### Synopsis
 
-<!-- AUTOGENERATED USAGE DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/bugs.js -->
-
 ```bash
 npm bugs [<pkgname> [<pkgname> ...]]
 
 alias: issues
 ```
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/bugs.js -->
-
-<!-- AUTOGENERATED USAGE DESCRIPTIONS END -->
-
 ### Description
 
 This command tries to guess at the likely location of a package's bug
@@ -30,9 +21,6 @@ will search for a `package.json` in the current folder and use the `name` proper
 
 ### Configuration
 
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
 #### `browser`
 
 * Default: OS X: `"open"`, Windows: `"start"`, Others: `"xdg-open"`
@@ -45,19 +33,13 @@ terminal.
 
 Set to `true` to use default system URL opener.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `registry`
 
 * Default: "https://registry.npmjs.org/"
 * Type: URL
 
 The base URL of the npm registry.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `workspace`
 
 * Default:
@@ -80,9 +62,6 @@ brand new workspace within the project.
 
 This value is not exported to the environment for child processes.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `workspaces`
 
 * Default: null
@@ -101,9 +80,6 @@ _unless_ one or more workspaces are specified in the `workspace` config.
 
 This value is not exported to the environment for child processes.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
 #### `include-workspace-root`
 
 * Default: false
@@ -117,11 +93,6 @@ the specified workspaces, and not on the root project.
 
 This value is not exported to the environment for child processes.
 
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
-
 ### See Also
 
 * [npm docs](/commands/npm-docs)