CLI documentation update from CI

Author: CI User

cli/v7

@@ -17,10 +17,10 @@ github_path: docs/content/commands/npm-cache.md
 ### Synopsis
 
 ```bash
-npm cache add <tarball file>
-npm cache add <folder>
-npm cache add <tarball url>
-npm cache add <name>@<version>
+npm cache add <tarball file>...
+npm cache add <folder>...
+npm cache add <tarball url>...
+npm cache add <name>@<version>...
 
 npm cache clean
 aliases: npm cache clear, npm cache rm
@@ -35,7 +35,7 @@ Note: This command is unaware of workspaces.
 Used to add, list, or clean the npm cache folder.
 
 * add:
-  Add the specified package to the local cache.  This command is primarily
+  Add the specified packages to the local cache.  This command is primarily
   intended to be used internally by npm, but it can provide a way to
   add data to the local installation cache explicitly.
 

content/cli/v7/commands/npm-cache.md

@@ -22,7 +22,7 @@ npm ci
 
 ### Description
 
-This command is similar to [`npm install`](/cli-commands/install), except
+This command is similar to [`npm install`](/cli/v7/commands/npm-install), except
 it's meant to be used in automated environments such as test platforms,
 continuous integration, and deployment -- or any situation where you want
 to make sure you're doing a clean install of your dependencies.

content/cli/v7/commands/npm-ci.md

@@ -84,7 +84,7 @@ Using `npm find-dupes` will run the command in `--dry-run` mode.
 
 ### See Also
 
-* [npm find-dupes](/cli-commands/find-dupes)
-* [npm ls](/cli-commands/ls)
-* [npm update](/cli-commands/update)
-* [npm install](/cli-commands/install)
+* [npm find-dupes](/cli/v7/commands/npm-find-dupes)
+* [npm ls](/cli/v7/commands/npm-ls)
+* [npm update](/cli/v7/commands/npm-update)
+* [npm install](/cli/v7/commands/npm-install)

content/cli/v7/commands/npm-dedupe.md

@@ -54,5 +54,5 @@ format an empty string.
 
 * [npm publish](/cli/v7/commands/npm-publish)
 * [npm registry](/cli/v7/using-npm/registry)
-* [npm owner](/cli-commands/owner)
-* [npm owner](/cli-commands/adduser)
+* [npm owner](/cli/v7/commands/npm-owner)
+* [npm owner](/cli/v7/commands/npm-adduser)

content/cli/v7/commands/npm-deprecate.md

@@ -54,5 +54,4 @@ The shell to run for the `npm explore` command.
 * [npm folders](/cli/v7/configuring-npm/folders)
 * [npm edit](/cli/v7/commands/npm-edit)
 * [npm rebuild](/cli/v7/commands/npm-rebuild)
-* [npm build](/cli/v7/commands/npm-build)
 * [npm install](/cli/v7/commands/npm-install)

content/cli/v7/commands/npm-explore.md

@@ -27,8 +27,8 @@ duplications, without actually changing the package tree.
 
 ### See Also
 
-* [npm dedupe](/cli-commands/dedupe)
-* [npm ls](/cli-commands/ls)
-* [npm update](/cli-commands/update)
-* [npm install](/cli-commands/install)
+* [npm dedupe](/cli/v7/commands/npm-dedupe)
+* [npm ls](/cli/v7/commands/npm-ls)
+* [npm update](/cli/v7/commands/npm-update)
+* [npm install](/cli/v7/commands/npm-install)
 

content/cli/v7/commands/npm-find-dupes.md

@@ -549,7 +549,6 @@ the specific folder structures that npm creates.
 * [npm link](/cli/v7/commands/npm-link)
 * [npm rebuild](/cli/v7/commands/npm-rebuild)
 * [npm scripts](/cli/v7/using-npm/scripts)
-* [npm build](/cli/v7/commands/npm-build)
 * [npm config](/cli/v7/commands/npm-config)
 * [npmrc](/cli/v7/configuring-npm/npmrc)
 * [npm registry](/cli/v7/using-npm/registry)

content/cli/v7/commands/npm-install.md

@@ -44,7 +44,7 @@ This removes a package version from the registry, deleting its entry and
 removing the tarball.
 
 The npm registry will return an error if you are not [logged
-in](/cli/v7/commands/npm-login).
+in](/cli/v7/commands/npm-adduser).
 
 If you do not specify a version or if you remove all of a package's
 versions then the registry will remove the root package entry entirely.
@@ -62,4 +62,4 @@ passed.
 * [npm registry](/cli/v7/using-npm/registry)
 * [npm adduser](/cli/v7/commands/npm-adduser)
 * [npm owner](/cli/v7/commands/npm-owner)
-* [npm login](/cli/v7/commands/npm-login)
+* [npm login](/cli/v7/commands/npm-adduser)

content/cli/v7/commands/npm-unpublish.md

@@ -83,7 +83,7 @@ npm view express contributors.name contributors.email
 
 "Person" fields are shown as a string if they would be shown as an
 object.  So, for example, this will show the list of `npm` contributors in
-the shortened string format.  (See [`package.json`](/cli/v7/configuring-npm/package.json) for more on this.)
+the shortened string format.  (See [`package.json`](/cli/v7/configuring-npm/package-json) for more on this.)
 
 ```bash
 npm view npm contributors

content/cli/v7/commands/npm-view.md

@@ -116,7 +116,7 @@ following help topics:
   Create an account or log in.  When you do this, npm will store
   credentials in the user config file config file.
 * publish:
-  Use the [`npm publish`](/cli/v7/commands/npm-publish`) command to upload your
+  Use the [`npm publish`](/cli/v7/commands/npm-publish) command to upload your
   code to the registry.
 
 #### Configuration

content/cli/v7/commands/npm.md

@@ -213,7 +213,7 @@ not be included in the package tarball.
 
 This allows a package maintainer to install all of their dependencies
 (and dev dependencies) locally, but only re-publish those items that
-cannot be found elsewhere.  See [`package.json`](/cli/v7/configuring-npm/package.json) for more information.
+cannot be found elsewhere.  See [`package.json`](/cli/v7/configuring-npm/package-json) for more information.
 
 ### See also
 

content/cli/v7/configuring-npm/folders.md

@@ -576,7 +576,7 @@ tarball or git URL.
 **Please do not put test harnesses or transpilers or other "development"
 time tools in your `dependencies` object.**  See `devDependencies`, below.
 
-See [semver](/cli/v7/using-npm/semver#versions) for more details about specifying version ranges.
+See [semver](https://github.com/npm/node-semver#versions) for more details about specifying version ranges.
 
 * `version` Must match `version` exactly
 * `>version` Must be greater than `version`

content/cli/v7/configuring-npm/package-json.md

@@ -1261,7 +1261,8 @@ Show short usage output about the command specified.
 
 #### `user-agent`
 
-* Default: "npm/{npm-version} node/{node-version} {platform} {arch} {ci}"
+* Default: "npm/{npm-version} node/{node-version} {platform} {arch}
+  workspaces/{workspaces} {ci}"
 * Type: String
 
 Sets the User-Agent request header. The following fields are replaced with
@@ -1271,6 +1272,8 @@ their actual counterparts:
 * `{node-version}` - The Node.js version in use
 * `{platform}` - The value of `process.platform`
 * `{arch}` - The value of `process.arch`
+* `{workspaces}` - Set to `true` if the `workspaces` or `workspace` options
+  are set.
 * `{ci}` - The value of the `ci-name` config, if set, prefixed with `ci/`, or
   an empty string if `ci-name` is empty.
 

content/cli/v7/using-npm/config.md

@@ -126,11 +126,6 @@ The advantage of doing these things at `prepublish` time is that they can be don
 
 * `prepare`
 
-#### [`npm env`](/cli/v7/commands/npm-env)
-
-* `env` (You can override the default behavior of `npm env` by defining
-    a custom `env` entry in your `scripts` object)
-
 #### [`npm install`](/cli/v7/commands/npm-install)
 
 These also run when you run `npm install -g <pkg-name>`
@@ -187,7 +182,7 @@ If there is a `restart` script defined, these events are run, otherwise
 * `restart`
 * `postrestart`
 
-#### [`npm run <user defined>`](/cli/v7/commands/npm-run)
+#### [`npm run <user defined>`](/cli/v7/commands/npm-run-script)
 
 * `pre<user-defined>`
 * `<user-defined>`