cbdc1c9 · cryptotaxi247/documentation-1

cli-cache.json

+1 -1

@@ -2,5 +2,5 @@

2 "v8": "aa8fff11cdab94fff1a2160ee5241f5f4632e96b",

3 "v9": "64763a341e7aa5b456e696f956759bf9b3440dc1",

4 "v10": "6755ca2d5301b079f9e2581fc72ba2a612171364",

5 - "v11": "5b4a7fc594e23dbdd5acab8df7bd195992383d5f"

5 + "v11": "072253549d774893a3689341dbc660cb845ebcfe"

6 }

\ No newline at end of file

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

+2 -12

@@ -55,17 +55,7 @@ Used to set access controls on private packages.

55

56 For all of the subcommands, `npm access` will perform actions on the packages in the current working directory if no package name is passed to the subcommand.

57

58 -- public / restricted (deprecated): Set a package to be either publicly accessible or restricted.

59 -

60 -- grant / revoke (deprecated): Add or remove the ability of users and teams to have read-only or read-write access to a package.

61 -

62 -- 2fa-required / 2fa-not-required (deprecated): Configure whether a package requires that anyone publishing it have two-factor authentication enabled on their account.

63 -

64 -- ls-packages (deprecated): Show all of the packages a user or a team is able to access, along with the access level, except for read-only public packages (it won't print the whole registry listing)

65 -

66 -- ls-collaborators (deprecated): Show all of the access privileges for a package. Will only show permissions for packages to which you have at least read access. If `<user>` is passed in, the list is filtered only to teams _that_ user happens to belong to.

67 -

68 -- edit (not implemented)

58 +- grant / revoke: Add or remove the ability of users and teams to have read-only or read-write access to a package.

59

60 ### Details

61

@@ -73,7 +63,7 @@ For all of the subcommands, `npm access` will perform actions on the packages in

63

64 Unscoped packages are _always public_.

65

76 -Scoped packages _default to restricted_, but you can either publish them as public using `npm publish --access=public`, or set their access as public using `npm access public` after the initial publish.

66 +Scoped packages _default to restricted_, but you can either publish them as public using `npm publish --access=public`, or set their access as public using `npm access set status=public` after the initial publish.

67

68 You must have privileges to set the access of a package:

69

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

+2 -2

@@ -102,7 +102,7 @@ The `sig` is generated using the following template: `${package.name}@${package.

102 Keys response:

103

104 - `expires`: null or a simplified extended [ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601): `YYYY-MM-DDTHH:mm:ss.sssZ`

105 -- `keydid`: sha256 fingerprint of the public key

105 +- `keyid`: sha256 fingerprint of the public key

106 - `keytype`: only `ecdsa-sha2-nistp256` is currently supported by the npm CLI

107 - `scheme`: only `ecdsa-sha2-nistp256` is currently supported by the npm CLI

108 - `key`: base64 encoded public key

@@ -285,7 +285,7 @@ If set to false, then ignore `package-lock.json` files when installing. This wil

285

286 #### `omit`

287

288 -- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production', otherwise empty.

288 +- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production'; otherwise, empty.

289 - Type: "dev", "optional", or "peer" (can be set multiple times)

290

291 Dependency types to omit from the installation tree on disk.

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

+1 -1

@@ -114,7 +114,7 @@ Only install direct dependencies in the top level `node_modules`, but hoist on d

114

115 #### `omit`

116

117 -- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production', otherwise empty.

117 +- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production'; otherwise, empty.

118 - Type: "dev", "optional", or "peer" (can be set multiple times)

119

120 Dependency types to omit from the installation tree on disk.

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

+1 -1

@@ -137,7 +137,7 @@ If set to false, then ignore `package-lock.json` files when installing. This wil

137

138 #### `omit`

139

140 -- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production', otherwise empty.

140 +- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production'; otherwise, empty.

141 - Type: "dev", "optional", or "peer" (can be set multiple times)

142

143 Dependency types to omit from the installation tree on disk.

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

+1 -1

@@ -90,7 +90,7 @@ If set to false, then ignore `package-lock.json` files when installing. This wil

90

91 #### `omit`

92

93 -- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production', otherwise empty.

93 +- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production'; otherwise, empty.

94 - Type: "dev", "optional", or "peer" (can be set multiple times)

95

96 Dependency types to omit from the installation tree on disk.

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

+1 -1

@@ -74,7 +74,7 @@ Only install direct dependencies in the top level `node_modules`, but hoist on d

74

75 #### `omit`

76

77 -- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production', otherwise empty.

77 +- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production'; otherwise, empty.

78 - Type: "dev", "optional", or "peer" (can be set multiple times)

79

80 Dependency types to omit from the installation tree on disk.

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

+1 -1

@@ -103,7 +103,7 @@ Only install direct dependencies in the top level `node_modules`, but hoist on d

103

104 #### `omit`

105

106 -- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production', otherwise empty.

106 +- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production'; otherwise, empty.

107 - Type: "dev", "optional", or "peer" (can be set multiple times)

108

109 Dependency types to omit from the installation tree on disk.

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

+1 -1

@@ -382,7 +382,7 @@ Only install direct dependencies in the top level `node_modules`, but hoist on d

382

383 #### `omit`

384

385 -- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production', otherwise empty.

385 +- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production'; otherwise, empty.

386 - Type: "dev", "optional", or "peer" (can be set multiple times)

387

388 Dependency types to omit from the installation tree on disk.

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

+1 -1

@@ -182,7 +182,7 @@ If set to false, then ignore `package-lock.json` files when installing. This wil

182

183 #### `omit`

184

185 -- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production', otherwise empty.

185 +- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production'; otherwise, empty.

186 - Type: "dev", "optional", or "peer" (can be set multiple times)

187

188 Dependency types to omit from the installation tree on disk.

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

+3 -3

@@ -52,7 +52,7 @@ Note: to get a "bottoms up" view of why a given package is included in the tree

52 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:

53

54 ```bash

55 -npm@11.6.1 /path/to/npm

55 +npm@11.6.2 /path/to/npm

56 └─┬ init-package-json@0.0.4

57 └── promzard@0.1.5

58 ```

@@ -112,7 +112,7 @@ Operates in "global" mode, so that packages are installed into the `prefix` fold

112

113 #### `depth`

114

115 -- Default: `Infinity` if `--all` is set, otherwise `0`

115 +- Default: `Infinity` if `--all` is set; otherwise, `0`

116 - Type: null or Number

117

118 The depth to go when recursing packages for `npm ls`.

@@ -121,7 +121,7 @@ If not set, `npm ls` will show only the immediate dependencies of the root proje

121

122 #### `omit`

123

124 -- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production', otherwise empty.

124 +- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production'; otherwise, empty.

125 - Type: "dev", "optional", or "peer" (can be set multiple times)

126

127 Dependency types to omit from the installation tree on disk.

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

+1 -1

@@ -59,7 +59,7 @@ In normal operation, extraneous modules are pruned automatically, so you'll only

59

60 #### `omit`

61

62 -- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production', otherwise empty.

62 +- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production'; otherwise, empty.

63 - Type: "dev", "optional", or "peer" (can be set multiple times)

64

65 Dependency types to omit from the installation tree on disk.

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

+3 -3

@@ -107,7 +107,7 @@ If used in the `npm publish` command, this is the tag that will be added to the

107

108 If you do not want your scoped package to be publicly viewable (and installable) set `--access=restricted`.

109

110 -Unscoped packages can not be set to `restricted`.

110 +Unscoped packages cannot be set to `restricted`.

111

112 Note: This defaults to not changing the current access level for existing packages. Specifying a value of `restricted` or `public` during publish will change the access for an existing package the same way that `npm access set status` would.

113

@@ -177,7 +177,7 @@ This value is not exported to the environment for child processes.

177

178 When publishing from a supported cloud CI/CD system, the package will be publicly linked to where it was built and published from.

179

180 -This config can not be used with: `provenance-file`

180 +This config cannot be used with: `provenance-file`

181

182 #### `provenance-file`

183

@@ -186,7 +186,7 @@ This config can not be used with: `provenance-file`

186

187 When publishing, the provenance bundle at the given path will be used.

188

189 -This config can not be used with: `provenance`

189 +This config cannot be used with: `provenance`

190

191 ### See Also

192

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

+2 -2

@@ -256,7 +256,7 @@ For `list` this means the output will be based on the tree described by the `pac

256

257 Tells npm whether or not to expect results from the command. Can be either true (expect some results) or false (expect no results).

258

259 -This config can not be used with: `expect-result-count`

259 +This config cannot be used with: `expect-result-count`

260

261 #### `expect-result-count`

262

@@ -265,7 +265,7 @@ This config can not be used with: `expect-result-count`

265

266 Tells to expect a specific number of results from the command.

267

268 -This config can not be used with: `expect-results`

268 +This config cannot be used with: `expect-results`

269

270 ## See Also

271

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

+1 -1

@@ -237,7 +237,7 @@ If package-lock-only is enabled, only the information in the package lock (or sh

237

238 #### `omit`

239

240 -- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production', otherwise empty.

240 +- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production'; otherwise, empty.

241 - Type: "dev", "optional", or "peer" (can be set multiple times)

242

243 Dependency types to omit from the installation tree on disk.

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

+1 -1

@@ -63,7 +63,7 @@ Publish token npm_… with id e0cf92 created 2017-10-02

63

64 - `npm token create [--read-only] [--cidr=<cidr-ranges>]`: Create a new authentication token. It can be `--read-only`, or accept a list of [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) ranges with which to limit use of this token. This will prompt you for your password, and, if you have two-factor authentication enabled, an otp.

65

66 - Currently, the cli can not generate automation tokens. Please refer to the [docs website](https://docs.npmjs.com/creating-and-viewing-access-tokens) for more information on generating automation tokens.

66 + Currently, the cli cannot generate automation tokens. Please refer to the [docs website](https://docs.npmjs.com/creating-and-viewing-access-tokens) for more information on generating automation tokens.

67

68 ```

69 Created publish token a73c9572-f1b9-8983-983d-ba3ac3cc913d

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

+1 -1

@@ -206,7 +206,7 @@ Only install direct dependencies in the top level `node_modules`, but hoist on d

206

207 #### `omit`

208

209 -- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production', otherwise empty.

209 +- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production'; otherwise, empty.

210 - Type: "dev", "optional", or "peer" (can be set multiple times)

211

212 Dependency types to omit from the installation tree on disk.

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

+1 -2

@@ -161,8 +161,7 @@ If the [`sign-git-tag` config](/cli/v11/using-npm/config#sign-git-tag) is set, t

161 $ npm config set sign-git-tag true

162 $ npm version patch

163

164 -You need a passphrase to unlock the secret key for

165 -user: "isaacs (http://blog.izs.me/) <i@izs.me>"

164 +You need a passphrase to unlock the secret key for user: "isaacs (http://blog.izs.me/) <i@izs.me>"

165 2048-bit RSA key, ID 6C481CF6, created 2010-08-31

166

167 Enter passphrase:

content/cli/v11/commands/npm.mdx

+2 -2

@@ -31,7 +31,7 @@ Note: This command is unaware of workspaces.

31

32 ### Version

33

34 -11.6.1

34 +11.6.2

35

36 ### Description

37

@@ -94,7 +94,7 @@ npm is extremely configurable. It reads its configuration options from 5 places.

94 - Global Configs: The file found at `./etc/npmrc` (relative to the global prefix will be parsed if it is found. See [`npm prefix`](/cli/v11/commands/npm-prefix) for more info on the global prefix. If the `globalconfig` option is set in the cli, env, or user config, then that file is parsed instead.

95 - Defaults: npm's default configuration options are defined in `lib/utils/config/definitions.js`. These must not be changed.

96

97 -See [`config`](/cli/v11/using-npm/config) for much much more information.

97 +See [`config`](/cli/v11/using-npm/config) for much, much, more information.

98

99 ### Contributions

100

content/cli/v11/configuring-npm/package-json.mdx

+3 -3

@@ -299,7 +299,7 @@ Most of these ignored files can be included specifically if included in the `fil

299 - `yarn.lock`

300 - `bun.lockb`

301

302 -These can not be included.

302 +These cannot be included.

303

304 ### exports

305

@@ -359,7 +359,7 @@ would be the same as this:

359 }

360 ```

361

362 -Please make sure that your file(s) referenced in `bin` starts with `#!/usr/bin/env node`, otherwise the scripts are started without the node executable!

362 +Please make sure that your file(s) referenced in `bin` starts with `#!/usr/bin/env node`; otherwise, the scripts are started without the node executable!

363

364 Note that you can also set the executable files using [directories.bin](#directoriesbin).

365

@@ -928,7 +928,7 @@ The `devEngines` field aids engineers working on a codebase to all be using the

928

929 You can specify a `devEngines` property in your `package.json` which will run before `install`, `ci`, and `run` commands.

930

931 -> Note: `engines` and `devEngines` differ in object shape. They also function very differently. `engines` is designed to alert the user when a dependency uses a differening npm or node version that the project it's being used in, whereas `devEngines` is used to alert people interacting with the source code of a project.

931 +> Note: `engines` and `devEngines` differ in object shape. They also function very differently. `engines` is designed to alert the user when a dependency uses a different npm or node version than the project it's being used in, whereas `devEngines` is used to alert people interacting with the source code of a project.

932

933 The supported keys under the `devEngines` property are `cpu`, `os`, `libc`, `runtime`, and `packageManager`. Each property can be an object or an array of objects. Objects must contain `name`, and optionally can specify `version`, and `onFail`. `onFail` can be `warn`, `error`, or `ignore`, and if left undefined is of the same value as `error`. `npm` will assume that you're running with `node`. Here's an example of a project that will fail if the environment is not `node` and `npm`. If you set `runtime.name` or `packageManager.name` to any other string, it will fail within the npm CLI.

934

content/cli/v11/using-npm/changelog.mdx

+55

@@ -15,6 +15,61 @@ redirect_from:

15 - /using-npm/changelog

16 ---

17

18 +## [11.6.2](https://github.com/npm/cli/compare/v11.6.1...v11.6.2) (2025-10-08)

19 +

20 +### Bug Fixes

21 +

22 +- [`c54d1e9`](https://github.com/npm/cli/commit/c54d1e96f37e7fd4bf2645c4905535c9b3d93e3b) [#8633](https://github.com/npm/cli/pull/8633) progress bar code cleanup (#8633) (@wraithgar)

23 +- [`d352e27`](https://github.com/npm/cli/commit/d352e27a679b1b7f4417ff5f7e3ac73fe13b403a) [#8629](https://github.com/npm/cli/pull/8629) do not redact notice logs going to stdout (#8629) (@wraithgar)

24 +- [`5ac3678`](https://github.com/npm/cli/commit/5ac3678feabbb28b1d0d8a78838bf8da79f63c1b) [#8617](https://github.com/npm/cli/pull/8617) spelling in ./lib and ./test/lib (#8617) (@jsoref)

25 +- [`9197995`](https://github.com/npm/cli/commit/9197995ef0b760738454f2d255c0683d0731b24c) [#8619](https://github.com/npm/cli/pull/8619) spelling (#8619) (@jsoref)

26 +- [`dd884e3`](https://github.com/npm/cli/commit/dd884e371c1fba7e2b7c1540baec405dd30ac3e7) [#8618](https://github.com/npm/cli/pull/8618) spelling (#8618) (@jsoref)

27 +- [`f6028e6`](https://github.com/npm/cli/commit/f6028e67aa1b2696e60e115d870182a026bae07f) [#8614](https://github.com/npm/cli/pull/8614) skip redacting urls meant for opening by the user (#8614) (@wraithgar, @jolyndenning)

28 +- [`54fd27f`](https://github.com/npm/cli/commit/54fd27f9f6af54ca9fd11165aafbc8a13a38f39e) [#8602](https://github.com/npm/cli/pull/8602) refactor node.ideallyInert to node.inert (#8602) (@liamcmitchell)

29 +- [`79e3c1e`](https://github.com/npm/cli/commit/79e3c1eff776ed7bbc76c1aa53b02cfdea40a6e7) [#8593](https://github.com/npm/cli/pull/8593) use @npmcli/package-json to normalize package data (@wraithgar)

30 +

31 +### Documentation

32 +

33 +- [`0469c5e`](https://github.com/npm/cli/commit/0469c5ebec7d4998f957d7c69702796af6797c57) [#8639](https://github.com/npm/cli/pull/8639) rewrap markdown (#8639) (@jsoref)

34 +- [`9ceb9c1`](https://github.com/npm/cli/commit/9ceb9c1d18d2c52a5c3328b4939e979baca7edea) [#8636](https://github.com/npm/cli/pull/8636) rewrap markdown (#8636) (@jsoref)

35 +- [`6324370`](https://github.com/npm/cli/commit/63243709429ab7d95f360caebce6c31946d41857) [#8616](https://github.com/npm/cli/pull/8616) fix spelling (#8616) (@jsoref)

36 +- [`1b0429a`](https://github.com/npm/cli/commit/1b0429af3b837e12fc5063d153393641435a856d) [#8607](https://github.com/npm/cli/pull/8607) Fix spelling (#8607) (@jsoref)

37 +- [`7fbe07a`](https://github.com/npm/cli/commit/7fbe07a6ad9eff81a41776fb6068fce9e7b557d1) [#8603](https://github.com/npm/cli/pull/8603) clean up deprecated `npm access` commands (#8603) (@jsoref)

38 +

39 +### Dependencies

40 +

41 +- [`fa7cc6f`](https://github.com/npm/cli/commit/fa7cc6f9338e6d9c0be1dbe7002d683fd389794a) [#8662](https://github.com/npm/cli/pull/8662) `ci-info@4.3.1` (#8662)

42 +- [`b05461b`](https://github.com/npm/cli/commit/b05461b6b16f262179efdea45fccf388f88ddc51) [#8663](https://github.com/npm/cli/pull/8663) `@sigstore/sign@4.0.1` (#8663)

43 +- [`c31de22`](https://github.com/npm/cli/commit/c31de22970930bedf43c1f92ff771bccf435271b) [#8661](https://github.com/npm/cli/pull/8661) downgrade ci-info to 4.3.0 (#8661) (@wraithgar)

44 +- [`c5191b5`](https://github.com/npm/cli/commit/c5191b542a9a49edf121be7127110e2958309df0) [#8659](https://github.com/npm/cli/pull/8659) `ci-info@4.3.1`

45 +- [`f255c92`](https://github.com/npm/cli/commit/f255c92abf6281af7b7f148b9683194ad09d9ba9) [#8659](https://github.com/npm/cli/pull/8659) `hosted-git-info@9.0.2`

46 +- [`bdaf323`](https://github.com/npm/cli/commit/bdaf323a160e47862ca228fa82e90555dcb567a8) [#8659](https://github.com/npm/cli/pull/8659) `is-cidr@6.0.1`

47 +- [`a33f106`](https://github.com/npm/cli/commit/a33f1062c3cacd889cea0d989de77a704931f54c) [#8659](https://github.com/npm/cli/pull/8659) `lru-cache@11.2.2`

48 +- [`8044e07`](https://github.com/npm/cli/commit/8044e07000c2b00e7db33693b1f7fb8e96978e02) [#8659](https://github.com/npm/cli/pull/8659) `npm-package-arg@13.0.1`

49 +- [`f577504`](https://github.com/npm/cli/commit/f5775043e7d2739256db20937ae072a1b1b3fb57) [#8659](https://github.com/npm/cli/pull/8659) `npm-packlist@10.0.2`

50 +- [`9aa4fa6`](https://github.com/npm/cli/commit/9aa4fa6687ee85a5c0085b3c3c96330eb9a9c7df) [#8659](https://github.com/npm/cli/pull/8659) `semver@7.7.3`

51 +- [`fe9484a`](https://github.com/npm/cli/commit/fe9484a17707f5a6bc16cdc91f29f848a4b54d31) [#8593](https://github.com/npm/cli/pull/8593) remove normalize-package-data

52 +

53 +### Chores

54 +

55 +- [`b3409f4`](https://github.com/npm/cli/commit/b3409f480fef2b9885fd071c951ad8313de2754e) [#8659](https://github.com/npm/cli/pull/8659) dev dependency updates (@wraithgar)

56 +- [`e8de81b`](https://github.com/npm/cli/commit/e8de81bc8202cfe1253676fd3f9785508e9051a6) [#8643](https://github.com/npm/cli/pull/8643) Add automatically generated annotation to dependencies.md (#8643) (@jsoref)

57 +- [`67cfaf3`](https://github.com/npm/cli/commit/67cfaf35295fa2f5d7aa01d37c423c60ad7afeca) [#8627](https://github.com/npm/cli/pull/8627) fix spelling: different (#8627) (@jsoref)

58 +- [`17ddc0d`](https://github.com/npm/cli/commit/17ddc0d6af1b56c4670b36b2c2705d31bdfa7749) [#8622](https://github.com/npm/cli/pull/8622) fix spelling (#8622) (@jsoref)

59 +- [`c3e1790`](https://github.com/npm/cli/commit/c3e1790c98d5c7fabc92bcfb1a5fa170f4c7fc1d) [#8605](https://github.com/npm/cli/pull/8605) Remove reference to nonexistent calendar (#8605) (@jsoref)

60 +- [`ac9143e`](https://github.com/npm/cli/commit/ac9143eafd46a89f707f525381b0ddb109b3beb6) [#8604](https://github.com/npm/cli/pull/8604) Improve link accessibility for screen reader users (#8604) (@jsoref)

61 +- [`62d73e7`](https://github.com/npm/cli/commit/62d73e763fa2deffa629a4451a80b7e58032b8e0) [#8601](https://github.com/npm/cli/pull/8601) remove references to benchmarks workflow (#8601) (@jsoref)

62 +- [`bb4b739`](https://github.com/npm/cli/commit/bb4b73953ada43285aa43dad626f48dafc53fea2) [#8598](https://github.com/npm/cli/pull/8598) remove stale comment (#8598) (@jsoref)

63 +- [`f73e65d`](https://github.com/npm/cli/commit/f73e65d86d425bcf6b1693553e981bd05d2daeaf) [#8592](https://github.com/npm/cli/pull/8592) fix build url code for remark-github@12 (#8592) (@wraithgar)

64 +- [workspace](https://github.com/npm/cli/releases/tag/arborist-v9.1.6): `@npmcli/arborist@9.1.6`

65 +- [workspace](https://github.com/npm/cli/releases/tag/config-v10.4.2): `@npmcli/config@10.4.2`

66 +- [workspace](https://github.com/npm/cli/releases/tag/libnpmaccess-v10.0.3): `libnpmaccess@10.0.3`

67 +- [workspace](https://github.com/npm/cli/releases/tag/libnpmdiff-v8.0.9): `libnpmdiff@8.0.9`

68 +- [workspace](https://github.com/npm/cli/releases/tag/libnpmexec-v10.1.8): `libnpmexec@10.1.8`

69 +- [workspace](https://github.com/npm/cli/releases/tag/libnpmfund-v7.0.9): `libnpmfund@7.0.9`

70 +- [workspace](https://github.com/npm/cli/releases/tag/libnpmpack-v9.0.9): `libnpmpack@9.0.9`

71 +- [workspace](https://github.com/npm/cli/releases/tag/libnpmpublish-v11.1.2): `libnpmpublish@11.1.2`

72 +

73 ## [11.6.1](https://github.com/npm/cli/compare/v11.6.0...v11.6.1) (2025-09-23)

74

75 ### Bug Fixes

content/cli/v11/using-npm/config.mdx

+12 -12

@@ -129,7 +129,7 @@ Warning: This should generally not be set via a command-line option. It is safer

129

130 If you do not want your scoped package to be publicly viewable (and installable) set `--access=restricted`.

131

132 -Unscoped packages can not be set to `restricted`.

132 +Unscoped packages cannot be set to `restricted`.

133

134 Note: This defaults to not changing the current access level for existing packages. Specifying a value of `restricted` or `public` during publish will change the access for an existing package the same way that `npm access set status` would.

135

@@ -274,7 +274,7 @@ Override CPU architecture of native modules to install. Acceptable values are sa

274

275 #### `depth`

276

277 -- Default: `Infinity` if `--all` is set, otherwise `0`

277 +- Default: `Infinity` if `--all` is set; otherwise, `0`

278 - Type: null or Number

279

280 The depth to go when recursing packages for `npm ls`.

@@ -378,7 +378,7 @@ This can be overridden by setting the `--force` flag.

378

379 Tells to expect a specific number of results from the command.

380

381 -This config can not be used with: `expect-results`

381 +This config cannot be used with: `expect-results`

382

383 #### `expect-results`

384

@@ -387,7 +387,7 @@ This config can not be used with: `expect-results`

387

388 Tells npm whether or not to expect results from the command. Can be either true (expect some results) or false (expect no results).

389

390 -This config can not be used with: `expect-result-count`

390 +This config cannot be used with: `expect-result-count`

391

392 #### `fetch-retries`

393

@@ -695,7 +695,7 @@ When set to "global" mode, packages are installed into the `prefix` folder inste

695

696 #### `lockfile-version`

697

698 -- Default: Version 3 if no lockfile, auto-converting v1 lockfiles to v3, otherwise maintain current lockfile version.

698 +- Default: Version 3 if no lockfile, auto-converting v1 lockfiles to v3; otherwise, maintain current lockfile version.

699 - Type: null, 1, 2, 3, "1", "2", or "3"

700

701 Set the lockfile format version to be used in package-lock.json and npm-shrinkwrap-json files. Possible options are:

@@ -790,7 +790,7 @@ Force offline mode: no network requests will be done during install. To allow th

790

791 #### `omit`

792

793 -- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production', otherwise empty.

793 +- Default: 'dev' if the `NODE_ENV` environment variable is set to 'production'; otherwise, empty.

794 - Type: "dev", "optional", or "peer" (can be set multiple times)

795

796 Dependency types to omit from the installation tree on disk.

@@ -914,7 +914,7 @@ Set to `false` to suppress the progress bar.

914

915 When publishing from a supported cloud CI/CD system, the package will be publicly linked to where it was built and published from.

916

917 -This config can not be used with: `provenance-file`

917 +This config cannot be used with: `provenance-file`

918

919 #### `provenance-file`

920

@@ -923,7 +923,7 @@ This config can not be used with: `provenance-file`

923

924 When publishing, the provenance bundle at the given path will be used.

925

926 -This config can not be used with: `provenance`

926 +This config cannot be used with: `provenance`

927

928 #### `proxy`

929

@@ -991,7 +991,7 @@ Ignored if `--save-peer` is set, since peerDependencies cannot be bundled.

991

992 Save installed packages to a package.json file as `devDependencies`.

993

994 -This config can not be used with: `save-optional`, `save-peer`, `save-prod`

994 +This config cannot be used with: `save-optional`, `save-peer`, `save-prod`

995

996 #### `save-exact`

997

@@ -1007,7 +1007,7 @@ Dependencies saved to package.json will be configured with an exact version rath

1007

1008 Save installed packages to a package.json file as `optionalDependencies`.

1009

1010 -This config can not be used with: `save-dev`, `save-peer`, `save-prod`

1010 +This config cannot be used with: `save-dev`, `save-peer`, `save-prod`

1011

1012 #### `save-peer`

1013

@@ -1016,7 +1016,7 @@ This config can not be used with: `save-dev`, `save-peer`, `save-prod`

1016

1017 Save installed packages to a package.json file as `peerDependencies`

1018

1019 -This config can not be used with: `save-dev`, `save-optional`, `save-prod`

1019 +This config cannot be used with: `save-dev`, `save-optional`, `save-prod`

1020

1021 #### `save-prefix`

1022

@@ -1036,7 +1036,7 @@ Save installed packages into `dependencies` specifically. This is useful if a pa

1036

1037 This is the default behavior if `--save` is true, and neither `--save-dev` or `--save-optional` are true.

1038

1039 -This config can not be used with: `save-dev`, `save-optional`, `save-peer`

1039 +This config cannot be used with: `save-dev`, `save-optional`, `save-peer`

1040

1041 #### `sbom-format`

1042

content/cli/v11/using-npm/dependency-selectors.mdx

+1 -1

@@ -159,7 +159,7 @@ The generic `:attr()` pseudo selector standardizes a pattern which can be used f

159 Nested objects are expressed as sequential arguments to `:attr()`.

160

161 ```css

162 -/* return dependencies that have a testling config for opera browsers */

162 +/* return dependencies that have a [testling config](https://ci.testling.com/guide/advanced_configuration) for opera browsers */

163 *: attr(testling, browsers, [~=opera]);

164 ```

165

content/cli/v11/using-npm/developers.mdx

+1 -1

@@ -134,7 +134,7 @@ More info at [`npm link`](/cli/v11/commands/npm-link).

134

135 **This is important.**

136

137 -If you can not install it locally, you'll have problems trying to publish it. Or, worse yet, you'll be able to publish it, but you'll be publishing a broken or pointless package. So don't do that.

137 +If you cannot install it locally, you'll have problems trying to publish it. Or, worse yet, you'll be able to publish it, but you'll be publishing a broken or pointless package. So don't do that.

138

139 In the root of your package, do this:

140

content/cli/v11/using-npm/orgs.mdx

+3 -3

@@ -85,19 +85,19 @@ npm access revoke <org:team> [<package>]

85 - See what org packages a team member can access:

86

87 ```bash

88 -npm access ls-packages <org> <user>

88 +npm access list packages <org> <user>

89 ```

90

91 - See packages available to a specific team:

92

93 ```bash

94 -npm access ls-packages <org:team>

94 +npm access list packages <org:team>

95 ```

96

97 - Check which teams are collaborating on a package:

98

99 ```bash

100 -npm access ls-collaborators <pkg>

100 +npm access list collaborators <pkg>

101 ```

102

103 ### See also

content/cli/v11/using-npm/scripts.mdx

+4 -4

@@ -65,7 +65,7 @@ There are some special life cycle scripts that happen only in certain situations

65 **prepack**

66

67 - Runs BEFORE a tarball is packed (on "`npm pack`", "`npm publish`", and when installing a git dependency).

68 -- NOTE: "`npm run pack`" is NOT the same as "`npm pack`". "`npm run pack`" is an arbitrary user defined script name, where as, "`npm pack`" is a CLI defined command.

68 +- NOTE: "`npm run pack`" is NOT the same as "`npm pack`". "`npm run pack`" is an arbitrary user defined script name, whereas, "`npm pack`" is a CLI defined command.

69

70 **postpack**

71

@@ -166,7 +166,7 @@ These are run from the scripts of `<pkg-name>`

166

167 #### [`npm restart`](/cli/v11/commands/npm-restart)

168

169 -If there is a `restart` script defined, these events are run, otherwise `stop` and `start` are both run if present, including their `pre` and `post` iterations)

169 +If there is a `restart` script defined, these events are run; otherwise, `stop` and `start` are both run if present, including their `pre` and `post` iterations)

170

171 - `prerestart`

172 - `restart`

@@ -211,8 +211,8 @@ While npm v6 had `uninstall` lifecycle scripts, npm v7 does not. Removal of a pa

211 Reasons for a package removal include:

212

213 - a user directly uninstalled this package

214 -- a user uninstalled a dependant package and so this dependency is being uninstalled

215 -- a user uninstalled a dependant package but another package also depends on this version

214 +- a user uninstalled a dependent package and so this dependency is being uninstalled

215 +- a user uninstalled a dependent package but another package also depends on this version

216 - this version has been merged as a duplicate with another version

217 - etc.

218

content/nav.yml

+1 -1

@@ -1596,7 +1596,7 @@

1596 - title: Changelog

1597 url: /cli/v10/using-npm/changelog

1598 description: Changelog notes for each version

1599 - - title: Version 11.6.1

1599 + - title: Version 11.6.2

1600 shortName: v11

1601 url: /cli/v11

1602 default: true

CLI documentation update from CI