CLI documentation update from CI
npm CLI robot committed
Jun 28, 2025 at 02:49 UTC
5e63545e86cb18c2cf0e207346cea4065295e342
4 files changed
+1
-7
cli-cache.json
+1
-1
@@ -2,5 +2,5 @@
2
"v8": "aa8fff11cdab94fff1a2160ee5241f5f4632e96b",
3
"v9": "64763a341e7aa5b456e696f956759bf9b3440dc1",
4
"v10": "f69c403700acb05dbb56d8516bca5130627e597c",
5
- "v11": "f163d011ade865b05b39b15aeee722809c223ae1"
5
+ "v11": "f7b056f28ac1a26fd875662768742df586c0b334"
6
}
\ No newline at end of file
content/cli/v11/commands/npm-install.mdx
-4
@@ -95,7 +95,6 @@ Even if you never publish your package, you can still get a lot of benefits of u
95
Install a package that is sitting on the filesystem. Note: if you just want to link a dev directory into your npm root, you can do this more easily by using [`npm link`](/cli/v11/commands/npm-link).
96
97
Tarball requirements:
98
-
98
- The filename _must_ use `.tar`, `.tar.gz`, or `.tgz` as the extension.
99
- The package contents should reside in a subfolder inside the tarball (usually it is called `package/`). npm strips one directory layer when installing the package (an equivalent of `tar x --strip-components=1` is run).
100
- The package must contain a `package.json` file with `name` and `version` properties.
@@ -129,7 +128,6 @@ Even if you never publish your package, you can still get a lot of benefits of u
128
```
129
130
`npm install` saves any specified packages into `dependencies` by default. Additionally, you can control where and how they get saved with some additional flags:
132
-
131
- `-P, --save-prod`: Package will appear in your `dependencies`. This is the default unless `-D` or `-O` are present.
132
133
- `-D, --save-dev`: Package will appear in your `devDependencies`.
@@ -141,7 +139,6 @@ Even if you never publish your package, you can still get a lot of benefits of u
139
- `--no-save`: Prevents saving to `dependencies`.
140
141
When using any of the above options to save dependencies to your package.json, there are two additional, optional flags:
144
-
142
- `-E, --save-exact`: Saved dependencies will be configured with an exact version rather than using npm's default semver range operator.
143
144
- `-B, --save-bundle`: Saved dependencies will also be added to your `bundleDependencies` list.
@@ -229,7 +226,6 @@ Even if you never publish your package, you can still get a lot of benefits of u
226
If the package being installed contains a `prepare` script, its `dependencies` and `devDependencies` will be installed, and the prepare script will be run, before the package is packaged and installed.
227
228
The following git environment variables are recognized by npm and will be added to the environment when running git:
232
-
229
- `GIT_ASKPASS`
230
- `GIT_EXEC_PATH`
231
- `GIT_PROXY_COMMAND`
content/cli/v11/commands/npm-profile.mdx
-1
@@ -70,7 +70,6 @@ updated: 2017-10-02T21:29:45.922Z
70
- `npm profile set password`: Change your password. This is interactive, you'll be prompted for your current password and a new password. You'll also be prompted for an OTP if you have two-factor authentication enabled.
71
72
- `npm profile enable-2fa [auth-and-writes|auth-only]`: Enables two-factor authentication. Defaults to `auth-and-writes` mode. Modes are:
73
-
73
- `auth-only`: Require an OTP when logging in or making changes to your account's authentication. The OTP will be required on both the website and the command line.
74
- `auth-and-writes`: Requires an OTP at all the times `auth-only` does, and also requires one when publishing a module, setting the `latest` dist-tag, or changing access via `npm access` and `npm owner`.
75
content/cli/v11/configuring-npm/package-lock-json.mdx
-1
@@ -131,7 +131,6 @@ npm v7 ignores this section entirely if a `packages` section is present, but doe
131
Dependency objects have the following fields:
132
133
- version: a specifier that varies depending on the nature of the package, and is usable in fetching a new copy of it.
134
-
134
- bundled dependencies: Regardless of source, this is a version number that is purely for informational purposes.
135
- registry sources: This is a version number. (eg, `1.2.3`)
136
- git sources: This is a git specifier with resolved committish. (eg, `git+https://example.com/foo/bar#115311855adb0789a0466714ed48a1499ffea97e`)