CLI documentation update from CI

Author: npm-cli-bot

cli-cache.json

@@ -2,5 +2,5 @@
   "v8": "aa8fff11cdab94fff1a2160ee5241f5f4632e96b",
   "v9": "64763a341e7aa5b456e696f956759bf9b3440dc1",
   "v10": "e510f14bf6a20d67e7b37c3f25ff271d9f7a0da5",
-  "v11": "b5173d13c182efa5434ef4ca413e62ce1437f47a"
+  "v11": "3d90a4936ec3324ff5b1642b20588c6d57ab04a5"
 }

content/cli/v11/commands/npm-adduser.mdx

@@ -49,6 +49,8 @@ Note: This command is unaware of workspaces.
 
 Create a new user in the specified registry, and save the credentials to the `.npmrc` file. If no registry is specified, the default registry will be used (see [`registry`](/cli/v11/using-npm/registry)).
 
+When you run `npm adduser`, the CLI automatically generates a legacy token of `publish` type. For more information, see [About legacy tokens](/about-access-tokens#about-legacy-tokens).
+
 When using `legacy` for your `auth-type`, the username, password, and email are read in from prompts.
 
 ### Configuration

content/cli/v11/commands/npm-audit.mdx

@@ -323,7 +323,7 @@ Note that this will generally make installs run slower, and be much noisier, but
 
 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.
+Note that commands explicitly intended to run a particular script, such as `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run` will still run their intended script if `ignore-scripts` is set, but they will _not_ run any pre- or post-scripts.
 
 #### `workspace`
 

content/cli/v11/commands/npm-ci.mdx

@@ -163,7 +163,7 @@ Note that this will generally make installs run slower, and be much noisier, but
 
 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.
+Note that commands explicitly intended to run a particular script, such as `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run` will still run their intended script if `ignore-scripts` is set, but they will _not_ run any pre- or post-scripts.
 
 #### `audit`
 

content/cli/v11/commands/npm-dedupe.mdx

@@ -166,7 +166,7 @@ Dependency types specified in `--include` will not be omitted, regardless of the
 
 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.
+Note that commands explicitly intended to run a particular script, such as `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run` will still run their intended script if `ignore-scripts` is set, but they will _not_ run any pre- or post-scripts.
 
 #### `audit`
 

content/cli/v11/commands/npm-exec.mdx

@@ -293,7 +293,7 @@ Run scripts in the context of all configured workspaces for the current project.
 
 ### See Also
 
-- [npm run-script](/cli/v11/commands/npm-run-script)
+- [npm run](/cli/v11/commands/npm-run)
 - [npm scripts](/cli/v11/using-npm/scripts)
 - [npm test](/cli/v11/commands/npm-test)
 - [npm start](/cli/v11/commands/npm-start)

content/cli/v11/commands/npm-find-dupes.mdx

@@ -119,7 +119,7 @@ Dependency types specified in `--include` will not be omitted, regardless of the
 
 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.
+Note that commands explicitly intended to run a particular script, such as `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run` will still run their intended script if `ignore-scripts` is set, but they will _not_ run any pre- or post-scripts.
 
 #### `audit`
 

content/cli/v11/commands/npm-init.mdx

@@ -103,6 +103,12 @@ Generate it without having it ask any questions:
 $ npm init -y
 ```
 
+Set the private flag to `true` in package.json:
+
+```bash
+$ npm init --init-private -y
+```
+
 ### Workspaces support
 
 It's possible to create a new workspace within your project by using the `workspace` config option. When using `npm init -w <dir>` the cli will create the folders and boilerplate expected while also adding a reference to your project `package.json` `"workspaces": []` property in order to make sure that new generated **workspace** is properly set up as such.
@@ -194,6 +200,13 @@ The value that `npm init` should use by default for the package.json type field.
 
 The value that `npm init` should use by default for the package version number, if not already set in package.json.
 
+#### `init-private`
+
+- Default: false
+- Type: Boolean
+
+The value `npm init` should use by default for the package's private flag.
+
 #### `yes`
 
 - Default: null

content/cli/v11/commands/npm-install-ci-test.mdx

@@ -123,7 +123,7 @@ Note that this will generally make installs run slower, and be much noisier, but
 
 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.
+Note that commands explicitly intended to run a particular script, such as `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run` will still run their intended script if `ignore-scripts` is set, but they will _not_ run any pre- or post-scripts.
 
 #### `audit`
 

content/cli/v11/commands/npm-install-test.mdx

@@ -177,7 +177,7 @@ Note that this will generally make installs run slower, and be much noisier, but
 
 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.
+Note that commands explicitly intended to run a particular script, such as `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run` will still run their intended script if `ignore-scripts` is set, but they will _not_ run any pre- or post-scripts.
 
 #### `audit`
 

content/cli/v11/commands/npm-install.mdx

@@ -460,7 +460,7 @@ Note that this will generally make installs run slower, and be much noisier, but
 
 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.
+Note that commands explicitly intended to run a particular script, such as `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run` will still run their intended script if `ignore-scripts` is set, but they will _not_ run any pre- or post-scripts.
 
 #### `audit`
 

content/cli/v11/commands/npm-link.mdx

@@ -211,7 +211,7 @@ Dependency types specified in `--include` will not be omitted, regardless of the
 
 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.
+Note that commands explicitly intended to run a particular script, such as `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run` will still run their intended script if `ignore-scripts` is set, but they will _not_ run any pre- or post-scripts.
 
 #### `audit`
 

content/cli/v11/commands/npm-login.mdx

@@ -47,6 +47,8 @@ Note: This command is unaware of workspaces.
 
 Verify a user in the specified registry, and save the credentials to the `.npmrc` file. If no registry is specified, the default registry will be used (see [`config`](/cli/v11/using-npm/config)).
 
+When you run `npm login`, the CLI automatically generates a legacy token of `publish` type. For more information, see [About legacy tokens](/about-access-tokens#about-legacy-tokens).
+
 When using `legacy` for your `auth-type`, the username and password, are read in from prompts.
 
 To reset your password, go to [https://www.npmjs.com/forgot](https://www.npmjs.com/forgot)

content/cli/v11/commands/npm-ls.mdx

@@ -52,7 +52,7 @@ Note: to get a "bottoms up" view of why a given package is included in the tree
 Positional arguments are `name@version-range` identifiers, which will limit the results to only the paths to the packages named. Note that nested 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@11.3.0 /path/to/npm
+npm@11.4.0 /path/to/npm
 └─┬ init-package-json@0.0.4
   └── promzard@0.1.5
 ```

content/cli/v11/commands/npm-outdated.mdx

@@ -55,6 +55,7 @@ In the output:
 - `depended by` shows which package depends on the displayed dependency
 - `package type` (when using `--long` / `-l`) tells you whether this package is a `dependency` or a dev/peer/optional dependency. Packages not included in `package.json` are always marked `dependencies`.
 - `homepage` (when using `--long` / `-l`) is the `homepage` value contained in the package's packument
+- `depended by location` (when using `--long` / `-l`) shows location of the package that depends on the displayed dependency
 - Red means there's a newer version matching your semver requirements, so you should update now.
 - Yellow indicates that there's a newer version _above_ your semver requirements (usually new major, or new 0.x minor) so proceed with caution.
 

content/cli/v11/commands/npm-pack.mdx

@@ -118,7 +118,7 @@ This value is not exported to the environment for child processes.
 
 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.
+Note that commands explicitly intended to run a particular script, such as `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run` will still run their intended script if `ignore-scripts` is set, but they will _not_ run any pre- or post-scripts.
 
 ### Description
 

content/cli/v11/commands/npm-prune.mdx

@@ -117,7 +117,7 @@ Note that this will generally make installs run slower, and be much noisier, but
 
 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.
+Note that commands explicitly intended to run a particular script, such as `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run` will still run their intended script if `ignore-scripts` is set, but they will _not_ run any pre- or post-scripts.
 
 #### `workspace`
 

content/cli/v11/commands/npm-rebuild.mdx

@@ -107,7 +107,7 @@ Note that this will generally make installs run slower, and be much noisier, but
 
 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.
+Note that commands explicitly intended to run a particular script, such as `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run` will still run their intended script if `ignore-scripts` is set, but they will _not_ run any pre- or post-scripts.
 
 #### `workspace`
 

content/cli/v11/commands/npm-restart.mdx

@@ -43,7 +43,7 @@ npm restart [-- <args>]
 
 ### Description
 
-This restarts a project. It is equivalent to running `npm run-script restart`.
+This restarts a project. It is equivalent to running `npm run restart`.
 
 If the current project has a `"restart"` script specified in `package.json`, then the following scripts will be run:
 
@@ -71,7 +71,7 @@ If it does _not_ have a `"restart"` script specified, but it does have `stop` an
 
 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.
+Note that commands explicitly intended to run a particular script, such as `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run` will still run their intended script if `ignore-scripts` is set, but they will _not_ run any pre- or post-scripts.
 
 #### `script-shell`
 
@@ -82,7 +82,7 @@ The shell to use for scripts run with the `npm exec`, `npm run` and `npm init <p
 
 ### See Also
 
-- [npm run-script](/cli/v11/commands/npm-run-script)
+- [npm run](/cli/v11/commands/npm-run)
 - [npm scripts](/cli/v11/using-npm/scripts)
 - [npm test](/cli/v11/commands/npm-test)
 - [npm start](/cli/v11/commands/npm-start)

content/cli/v11/commands/npm-run-script.mdx renamed to content/cli/v11/commands/npm-run.mdx

@@ -1,46 +1,46 @@
 ---
-title: npm-run-script
+title: npm-run
 section: 1
 description: Run arbitrary package scripts
 github_repo: npm/cli
 github_branch: latest
-github_path: docs/lib/content/commands/npm-run-script.md
+github_path: docs/lib/content/commands/npm-run.md
 redirect_from:
-  - /cli-commands/npm-run-script
-  - /cli-commands/run-script
-  - /cli-documentation/cli-commands/npm-run-script
-  - /cli-documentation/cli-commands/run-script
-  - /cli-documentation/commands/npm-run-script
-  - /cli-documentation/commands/run-script
-  - /cli-documentation/npm-run-script
-  - /cli-documentation/run-script
-  - /cli-documentation/v11/cli-commands/npm-run-script
-  - /cli-documentation/v11/cli-commands/run-script
-  - /cli-documentation/v11/commands/npm-run-script
-  - /cli-documentation/v11/commands/run-script
-  - /cli-documentation/v11/npm-run-script
-  - /cli-documentation/v11/run-script
-  - /cli/cli-commands/npm-run-script
-  - /cli/cli-commands/run-script
-  - /cli/commands/npm-run-script
-  - /cli/commands/run-script
-  - /cli/npm-run-script
-  - /cli/run-script
-  - /cli/v11/cli-commands/npm-run-script
-  - /cli/v11/cli-commands/run-script
-  - /cli/v11/commands/run-script
-  - /cli/v11/npm-run-script
-  - /cli/v11/run-script
-  - /commands/npm-run-script
-  - /commands/run-script
+  - /cli-commands/npm-run
+  - /cli-commands/run
+  - /cli-documentation/cli-commands/npm-run
+  - /cli-documentation/cli-commands/run
+  - /cli-documentation/commands/npm-run
+  - /cli-documentation/commands/run
+  - /cli-documentation/npm-run
+  - /cli-documentation/run
+  - /cli-documentation/v11/cli-commands/npm-run
+  - /cli-documentation/v11/cli-commands/run
+  - /cli-documentation/v11/commands/npm-run
+  - /cli-documentation/v11/commands/run
+  - /cli-documentation/v11/npm-run
+  - /cli-documentation/v11/run
+  - /cli/cli-commands/npm-run
+  - /cli/cli-commands/run
+  - /cli/commands/npm-run
+  - /cli/commands/run
+  - /cli/npm-run
+  - /cli/run
+  - /cli/v11/cli-commands/npm-run
+  - /cli/v11/cli-commands/run
+  - /cli/v11/commands/run
+  - /cli/v11/npm-run
+  - /cli/v11/run
+  - /commands/npm-run
+  - /commands/run
 ---
 
 ### Synopsis
 
 ```bash
-npm run-script <command> [-- <args>]
+npm run <command> [-- <args>]
 
-aliases: run, rum, urn
+aliases: run-script, rum, urn
 ```
 
 ### Description
@@ -177,7 +177,7 @@ This value is not exported to the environment for child processes.
 - Default: false
 - Type: Boolean
 
-If true, npm will not exit with an error code when `run-script` is invoked for a script that isn't defined in the `scripts` section of `package.json`. This option can be used when it's desirable to optionally run a script when it's present and fail if the script fails. This is useful, for example, when running scripts that may only apply for some builds in an otherwise generic CI setup.
+If true, npm will not exit with an error code when `run` is invoked for a script that isn't defined in the `scripts` section of `package.json`. This option can be used when it's desirable to optionally run a script when it's present and fail if the script fails. This is useful, for example, when running scripts that may only apply for some builds in an otherwise generic CI setup.
 
 This value is not exported to the environment for child processes.
 
@@ -188,7 +188,7 @@ This value is not exported to the environment for child processes.
 
 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.
+Note that commands explicitly intended to run a particular script, such as `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run` will still run their intended script if `ignore-scripts` is set, but they will _not_ run any pre- or post-scripts.
 
 #### `foreground-scripts`
 

content/cli/v11/commands/npm-shrinkwrap.mdx

@@ -50,7 +50,7 @@ This command repurposes `package-lock.json` into a publishable `npm-shrinkwrap.j
 ### See Also
 
 - [npm install](/cli/v11/commands/npm-install)
-- [npm run-script](/cli/v11/commands/npm-run-script)
+- [npm run](/cli/v11/commands/npm-run)
 - [npm scripts](/cli/v11/using-npm/scripts)
 - [package.json](/cli/v11/configuring-npm/package-json)
 - [package-lock.json](/cli/v11/configuring-npm/package-lock-json)

content/cli/v11/commands/npm-start.mdx

@@ -49,7 +49,7 @@ If the `"scripts"` object does not define a `"start"` property, npm will run `no
 
 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 [`npm@2.0.0`](https://blog.npmjs.org/post/98131109725/npm-2-0-0), you can use custom arguments when executing scripts. Refer to [`npm run-script`](/cli/v11/commands/npm-run-script) for more details.
+As of [`npm@2.0.0`](https://blog.npmjs.org/post/98131109725/npm-2-0-0), you can use custom arguments when executing scripts. Refer to [`npm run`](/cli/v11/commands/npm-run) for more details.
 
 ### Example
 
@@ -80,7 +80,7 @@ npm start
 
 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.
+Note that commands explicitly intended to run a particular script, such as `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run` will still run their intended script if `ignore-scripts` is set, but they will _not_ run any pre- or post-scripts.
 
 #### `script-shell`
 
@@ -91,7 +91,7 @@ The shell to use for scripts run with the `npm exec`, `npm run` and `npm init <p
 
 ### See Also
 
-- [npm run-script](/cli/v11/commands/npm-run-script)
+- [npm run](/cli/v11/commands/npm-run)
 - [npm scripts](/cli/v11/using-npm/scripts)
 - [npm test](/cli/v11/commands/npm-test)
 - [npm restart](/cli/v11/commands/npm-restart)

content/cli/v11/commands/npm-stop.mdx

@@ -76,7 +76,7 @@ npm stop
 
 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.
+Note that commands explicitly intended to run a particular script, such as `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run` will still run their intended script if `ignore-scripts` is set, but they will _not_ run any pre- or post-scripts.
 
 #### `script-shell`
 
@@ -87,7 +87,7 @@ The shell to use for scripts run with the `npm exec`, `npm run` and `npm init <p
 
 ### See Also
 
-- [npm run-script](/cli/v11/commands/npm-run-script)
+- [npm run](/cli/v11/commands/npm-run)
 - [npm scripts](/cli/v11/using-npm/scripts)
 - [npm test](/cli/v11/commands/npm-test)
 - [npm start](/cli/v11/commands/npm-start)