CLI documentation update from CI

npm-cli-bot · npm-cli-bot · commit 30c583b99504 · 2022-08-03T03:05:28.000Z
diff --git a/cli/v8 b/cli/v8
@@ -1 +1 @@
-Subproject commit 3c024ace60904c69e61da00e1fb56c0c1735804a
+Subproject commit 3b30af25e93665f5aa21897910a65d7f26bbd066
diff --git a/content/cli/v8/commands/npm-exec.md b/content/cli/v8/commands/npm-exec.md
@@ -137,7 +137,7 @@ $ npm exec -- foo@latest bar --package=@npmcli/foo
 * Default:
 * Type: String (can be set multiple times)
 
-The package to install for [`npm exec`](/cli/v8/commands/npm-exec)
+The package or packages to install for [`npm exec`](/cli/v8/commands/npm-exec)
 
 <!-- automatically generated, do not edit manually -->
 <!-- see lib/utils/config/definitions.js -->
diff --git a/content/cli/v8/using-npm/config.md b/content/cli/v8/using-npm/config.md
@@ -1252,7 +1252,7 @@ Directory in which `npm pack` will save tarballs.
 * Default:
 * Type: String (can be set multiple times)
 
-The package to install for [`npm exec`](/cli/v8/commands/npm-exec)
+The package or packages to install for [`npm exec`](/cli/v8/commands/npm-exec)
 
 <!-- automatically generated, do not edit manually -->
 <!-- see lib/utils/config/definitions.js -->
@@ -1401,6 +1401,24 @@ The base URL of the npm registry.
 <!-- automatically generated, do not edit manually -->
 <!-- see lib/utils/config/definitions.js -->
 
+#### `replace-registry-host`
+
+* Default: "npmjs"
+* Type: "npmjs", "never", "always", or String
+
+Defines behavior for replacing the registry host in a lockfile with the
+configured registry.
+
+The default behavior is to replace package dist URLs from the default
+registry (https://registry.npmjs.org) to the configured registry. If set to
+"never", then use the registry value. If set to "always", then replace the
+registry host with the configured host every time.
+
+You may also specify a bare hostname (e.g., "registry.npmjs.org").
+
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 #### `save`
 
 * Default: `true` unless when using `npm update` where it defaults to `false`
