deps: upgrade npm to 9.7.1

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

@@ -90,6 +90,8 @@ Whether or not to output JSON data, rather than the normal output.
 
 Not supported by all npm commands.
 
+
+
 #### `otp`
 
 * Default: null
@@ -101,13 +103,17 @@ 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.
 
+
+
 #### `registry`
 
 * Default: "https://registry.npmjs.org/"
 * Type: URL
 
 The base URL of the npm registry.
 
+
+
 ### See Also
 
 * [`libnpmaccess`](https://npm.im/libnpmaccess)

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

@@ -32,6 +32,8 @@ email are read in from prompts.
 
 The base URL of the npm registry.
 
+
+
 #### `scope`
 
 * Default: the scope of the current project, if any, or ""
@@ -62,6 +64,7 @@ npm init --scope=@foo --yes
 ```
 
 
+
 #### `auth-type`
 
 * Default: "web"
@@ -70,6 +73,8 @@ npm init --scope=@foo --yes
 What authentication strategy to use with `login`. Note that if an `otp`
 config is given, this value will always be set to `legacy`.
 
+
+
 ### See Also
 
 * [npm registry](/using-npm/registry)

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

@@ -246,6 +246,8 @@ $ npm audit --audit-level=moderate
 The minimum level of vulnerability for `npm audit` to exit with a non-zero
 exit code.
 
+
+
 #### `dry-run`
 
 * Default: false
@@ -259,6 +261,8 @@ commands that modify your local installation, eg, `install`, `update`,
 Note: This is NOT honored by other network related commands, eg `dist-tags`,
 `owner`, etc.
 
+
+
 #### `force`
 
 * Default: false
@@ -285,6 +289,8 @@ 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!
 
+
+
 #### `json`
 
 * Default: false
@@ -297,6 +303,8 @@ Whether or not to output JSON data, rather than the normal output.
 
 Not supported by all npm commands.
 
+
+
 #### `package-lock-only`
 
 * Default: false
@@ -311,6 +319,8 @@ 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`.
 
+
+
 #### `omit`
 
 * Default: 'dev' if the `NODE_ENV` environment variable is set to
@@ -329,6 +339,8 @@ 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.
 
+
+
 #### `foreground-scripts`
 
 * Default: false
@@ -341,6 +353,8 @@ 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.
 
+
+
 #### `ignore-scripts`
 
 * Default: false
@@ -353,6 +367,8 @@ 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.
 
+
+
 #### `workspace`
 
 * Default:
@@ -415,6 +431,8 @@ When set file: protocol dependencies will be packed and installed as regular
 dependencies instead of creating a symlink. This option has no effect on
 workspaces.
 
+
+
 ### See Also
 
 * [npm install](/commands/npm-install)

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

@@ -34,13 +34,17 @@ terminal.
 
 Set to `true` to use default system URL opener.
 
+
+
 #### `registry`
 
 * Default: "https://registry.npmjs.org/"
 * Type: URL
 
 The base URL of the npm registry.
 
+
+
 #### `workspace`
 
 * Default:

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

@@ -77,6 +77,8 @@ verify`.
 
 The location of npm's cache directory.
 
+
+
 ### See Also
 
 * [package spec](/using-npm/package-spec)

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

@@ -84,6 +84,8 @@ place, no hoisting. shallow (formerly --global-style) only install direct
 deps at top-level. linked: (experimental) install in node_modules/.store,
 link in place, unhoisted.
 
+
+
 #### `legacy-bundling`
 
 * Default: false
@@ -96,6 +98,8 @@ the same manner that they are depended on. This may cause very deep
 directory structures and duplicate package installs as there is no
 de-duplicating. Sets `--install-strategy=nested`.
 
+
+
 #### `global-style`
 
 * Default: false
@@ -106,6 +110,8 @@ de-duplicating. Sets `--install-strategy=nested`.
 Only install direct dependencies in the top level `node_modules`, but hoist
 on deeper dependencies. Sets `--install-strategy=shallow`.
 
+
+
 #### `omit`
 
 * Default: 'dev' if the `NODE_ENV` environment variable is set to
@@ -124,6 +130,8 @@ 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.
 
+
+
 #### `strict-peer-deps`
 
 * Default: false
@@ -143,15 +151,7 @@ When such an override is performed, a warning is printed, explaining the
 conflict and the packages involved. If `--strict-peer-deps` is set, then
 this warning is treated as a failure.
 
-#### `package-lock`
-
-* Default: true
-* Type: Boolean
-
-If set to false, then ignore `package-lock.json` files when installing. This
-will also prevent _writing_ `package-lock.json` if `save` is true.
 
-This configuration does not affect `npm ci`.
 
 #### `foreground-scripts`
 
@@ -165,6 +165,8 @@ 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.
 
+
+
 #### `ignore-scripts`
 
 * Default: false
@@ -177,6 +179,8 @@ 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.
 
+
+
 #### `audit`
 
 * Default: true
@@ -187,6 +191,8 @@ default registry and all registries configured for scopes. See the
 documentation for [`npm audit`](/commands/npm-audit) for details on what is
 submitted.
 
+
+
 #### `bin-links`
 
 * Default: true
@@ -199,6 +205,8 @@ Set to false to have it not do this. This can be used to work around the
 fact that some file systems don't support symlinks, even on ostensibly Unix
 systems.
 
+
+
 #### `fund`
 
 * Default: true
@@ -208,6 +216,8 @@ When "true" displays the message at the end of each `npm install`
 acknowledging the number of dependencies looking for funding. See [`npm
 fund`](/commands/npm-fund) for details.
 
+
+
 #### `dry-run`
 
 * Default: false
@@ -221,6 +231,8 @@ commands that modify your local installation, eg, `install`, `update`,
 Note: This is NOT honored by other network related commands, eg `dist-tags`,
 `owner`, etc.
 
+
+
 #### `workspace`
 
 * Default:
@@ -283,6 +295,8 @@ When set file: protocol dependencies will be packed and installed as regular
 dependencies instead of creating a symlink. This option has no effect on
 workspaces.
 
+
+
 ### See Also
 
 * [npm install](/commands/npm-install)

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

@@ -116,6 +116,8 @@ Whether or not to output JSON data, rather than the normal output.
 
 Not supported by all npm commands.
 
+
+
 #### `global`
 
 * Default: false
@@ -130,6 +132,8 @@ folder instead of the current working directory. See
 * bin files are linked to `{prefix}/bin`
 * man pages are linked to `{prefix}/share/man`
 
+
+
 #### `editor`
 
 * Default: The EDITOR or VISUAL environment variables, or
@@ -138,6 +142,8 @@ folder instead of the current working directory. See
 
 The command to run for `npm edit` and `npm config edit`.
 
+
+
 #### `location`
 
 * Default: "user" unless `--global` is passed, which will also set this value
@@ -155,13 +161,17 @@ instead of the current working directory. See
 * bin files are linked to `{prefix}/bin`
 * man pages are linked to `{prefix}/share/man`
 
+
+
 #### `long`
 
 * Default: false
 * Type: Boolean
 
 Show extended information in `ls`, `search`, and `help-search`.
 
+
+
 ### See Also
 
 * [npm folders](/configuring-npm/folders)