@cryptotaxi247 / documentation / commits / 540d1cf

CLI documentation update from CI

npm CLI robot committed Jan 29, 2025 at 21:20 UTC 540d1cf5f1c874018951b25f75a3d625b06263f0

9 files changed +188 -57

cli-cache.json

+1 -1

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

2 "v8": "aa8fff11cdab94fff1a2160ee5241f5f4632e96b",

3 "v9": "64763a341e7aa5b456e696f956759bf9b3440dc1",

4 "v10": "a3041941586b6fb8ed7403fe3c24d81138a96005",

5 - "v11": "6d0f46e67e9673e8a2dc6edb92144a73f853950c"

5 + "v11": "cab74ff7c25149d172cf5d612eb0a651eda531e3"

6 }

\ No newline at end of file

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

@@ -83,6 +83,15 @@ This is a one-time password from a two-factor authenticator. It's needed when pu

84 If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.

86 +#### `dry-run`

87 +

88 +- Default: false

89 +- Type: Boolean

90 +

91 +Indicates that you don't want npm to make any changes and that it should only report what it would have done. This can be passed into any of the commands that modify your local installation, eg, `install`, `update`, `dedupe`, `uninstall`, as well as `pack` and `publish`.

92 +

93 +Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc.

94 +

95 ### See Also

97 - [package spec](/cli/v11/using-npm/package-spec)

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

+2 -2

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

54 ```bash

55 -npm@11.0.0 /path/to/npm

55 +npm@11.1.0 /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 `1`

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`.

content/cli/v11/commands/npm-undeprecate.mdx new

+81

@@ -0,0 +1,81 @@

1 +---

2 +title: npm-undeprecate

3 +section: 1

4 +description: Undeprecate a version of a package

5 +github_repo: npm/cli

6 +github_branch: latest

7 +github_path: docs/lib/content/commands/npm-undeprecate.md

8 +redirect_from:

9 + - /cli-commands/npm-undeprecate

10 + - /cli-commands/undeprecate

11 + - /cli-documentation/cli-commands/npm-undeprecate

12 + - /cli-documentation/cli-commands/undeprecate

13 + - /cli-documentation/commands/npm-undeprecate

14 + - /cli-documentation/commands/undeprecate

15 + - /cli-documentation/npm-undeprecate

16 + - /cli-documentation/undeprecate

17 + - /cli-documentation/v11/cli-commands/npm-undeprecate

18 + - /cli-documentation/v11/cli-commands/undeprecate

19 + - /cli-documentation/v11/commands/npm-undeprecate

20 + - /cli-documentation/v11/commands/undeprecate

21 + - /cli-documentation/v11/npm-undeprecate

22 + - /cli-documentation/v11/undeprecate

23 + - /cli/cli-commands/npm-undeprecate

24 + - /cli/cli-commands/undeprecate

25 + - /cli/commands/npm-undeprecate

26 + - /cli/commands/undeprecate

27 + - /cli/npm-undeprecate

28 + - /cli/undeprecate

29 + - /cli/v11/cli-commands/npm-undeprecate

30 + - /cli/v11/cli-commands/undeprecate

31 + - /cli/v11/commands/undeprecate

32 + - /cli/v11/npm-undeprecate

33 + - /cli/v11/undeprecate

34 + - /commands/npm-undeprecate

35 + - /commands/undeprecate

36 +---

37 +

38 +### Synopsis

39 +

40 +```bash

41 +npm undeprecate <package-spec>

42 +```

43 +

44 +Note: This command is unaware of workspaces.

45 +

46 +### Description

47 +

48 +This command will update the npm registry entry for a package, removing any deprecation warnings that currently exist.

49 +

50 +It works in the same way as [npm deprecate](/cli/v11/commands/npm-deprecate), except that this command removes deprecation warnings instead of adding them.

51 +

52 +### Configuration

53 +

54 +#### `registry`

55 +

56 +- Default: "https://registry.npmjs.org/"

57 +- Type: URL

58 +

59 +The base URL of the npm registry.

60 +

61 +#### `otp`

62 +

63 +- Default: null

64 +- Type: null or String

65 +

66 +This is a one-time password from a two-factor authenticator. It's needed when publishing or changing package permissions with `npm access`.

67 +

68 +If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.

69 +

70 +#### `dry-run`

71 +

72 +- Default: false

73 +- Type: Boolean

74 +

75 +Indicates that you don't want npm to make any changes and that it should only report what it would have done. This can be passed into any of the commands that modify your local installation, eg, `install`, `update`, `dedupe`, `uninstall`, as well as `pack` and `publish`.

76 +

77 +Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc.

78 +

79 +### See Also

80 +

81 +- [npm deprecate](/cli/v11/commands/npm-deprecate)

content/cli/v11/commands/npm.mdx

+1 -1

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

32 ### Version

34 -11.0.0

34 +11.1.0

36 ### Description

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

+51 -51

@@ -53,7 +53,7 @@ Some tips:

53 - The name will probably be passed as an argument to require(), so it should be something short, but also reasonably descriptive.

54 - You may want to check the npm registry to see if there's something by that name already, before you get too attached to it. [https://www.npmjs.com/](https://www.npmjs.com/)

56 -A name can be optionally prefixed by a scope, e.g. `@myorg/mypackage`. See [`scope`](/cli/v11/using-npm/scope) for more detail.

56 +A name can be optionally prefixed by a scope, e.g. `@npm/example`. See [`scope`](/cli/v11/using-npm/scope) for more detail.

58 ### version

@@ -76,7 +76,7 @@ The URL to the project homepage.

76 Example:

78 ```json

79 -"homepage": "https://github.com/owner/project#readme"

79 +"homepage": "https://github.com/npm/example#readme"

80 ```

82 ### bugs

@@ -88,8 +88,8 @@ It should look like this:

88 ```json

89 {

90 "bugs": {

91 - "url": "https://github.com/owner/project/issues",

92 - "email": "project@hostname.com"

91 + "url": "https://github.com/npm/example/issues",

92 + "email": "example@npmjs.com"

93 }

94 }

95 ```

@@ -110,7 +110,7 @@ If you're using a common license such as BSD-2-Clause or MIT, add a current SPDX

110 }

111 ```

112

113 -You can check [the full list of SPDX license IDs](https://spdx.org/licenses/). Ideally you should pick one that is [OSI](https://opensource.org/licenses/) approved.

113 +You can check [the full list of SPDX license IDs](https://spdx.org/licenses/). Ideally, you should pick one that is [OSI](https://opensource.org/licenses/) approved.

114

115 If your package is licensed under multiple common licenses, use an [SPDX license expression syntax version 2.0 string](https://spdx.dev/specifications/), like this:

116

@@ -187,8 +187,8 @@ The "author" is one person. "contributors" is an array of people. A "person" is

187 ```json

188 {

189 "name": "Barney Rubble",

190 - "email": "b@rubble.com",

191 - "url": "http://barnyrubble.tumblr.com/"

190 + "email": "barney@npmjs.com",

191 + "url": "http://barnyrubble.npmjs.com/"

192 }

193 ```

194

@@ -196,7 +196,7 @@ Or you can shorten that all into a single string, and npm will parse it for you:

196

197 ```json

198 {

199 - "author": "Barney Rubble <b@rubble.com> (http://barnyrubble.tumblr.com/)"

199 + "author": "Barney Rubble <barney@npmjs.com> (http://barnyrubble.npmjs.com/)"

200 }

201 ```

202

@@ -212,7 +212,7 @@ You can specify an object containing a URL that provides up-to-date information

212 {

213 "funding": {

214 "type": "individual",

215 - "url": "http://example.com/donate"

215 + "url": "http://npmjs.com/donate"

216 }

217 }

218 ```

@@ -221,14 +221,14 @@ You can specify an object containing a URL that provides up-to-date information

221 {

222 "funding": {

223 "type": "patreon",

224 - "url": "https://www.patreon.com/my-account"

224 + "url": "https://www.patreon.com/user"

225 }

226 }

227 ```

228

229 ```json

230 {

231 - "funding": "http://example.com/donate"

231 + "funding": "http://npmjs.com/donate"

232 }

233 ```

234

@@ -237,12 +237,12 @@ You can specify an object containing a URL that provides up-to-date information

237 "funding": [

238 {

239 "type": "individual",

240 - "url": "http://example.com/donate"

240 + "url": "http://npmjs.com/donate"

241 },

242 - "http://example.com/donateAlso",

242 + "http://npmjs.com/donate-also",

243 {

244 "type": "patreon",

245 - "url": "https://www.patreon.com/my-account"

245 + "url": "https://www.patreon.com/user"

246 }

247 ]

248 }

@@ -448,9 +448,9 @@ For GitHub, GitHub gist, Bitbucket, or GitLab repositories you can use the same

448

449 ```json

450 {

451 - "repository": "npm/npm",

451 + "repository": "npm/example",

452

453 - "repository": "github:user/repo",

453 + "repository": "github:npm/example",

454

455 "repository": "gist:11081aaa281",

456

@@ -518,7 +518,7 @@ See [semver](https://github.com/npm/node-semver#versions) for more details about

518 - `user/repo` See 'GitHub URLs' below

519 - `tag` A specific version tagged and published as `tag` See [`npm dist-tag`](/cli/v11/commands/npm-dist-tag)

520 - `path/path/path` See [Local Paths](#local-paths) below

521 -- `npm:@scope/pkg@version` Custom alias for a pacakge See [`package-spec`](/cli/v11/using-npm/package-spec#aliases)

521 +- `npm:@scope/pkg@version` Custom alias for a package See [`package-spec`](/cli/v11/using-npm/package-spec#aliases)

522

523 For example, these are all valid:

524

@@ -530,7 +530,7 @@ For example, these are all valid:

530 "baz": ">1.0.2 <=2.3.4",

531 "boo": "2.0.1",

532 "qux": "<1.0.0 || >=2.3.1 <2.4.5 || >=2.5.2 <3.0.0",

533 - "asd": "http://asdf.com/asdf.tar.gz",

533 + "asd": "http://npmjs.com/example.tar.gz",

534 "til": "~1.2",

535 "elf": "~1.2.3",

536 "two": "2.x",

@@ -593,7 +593,7 @@ As of version 1.1.65, you can refer to GitHub URLs as just "foo": "user/foo-proj

593 "dependencies": {

594 "express": "expressjs/express",

595 "mocha": "mochajs/mocha#4727d357ea",

596 - "module": "user/repo#feature\/branch"

596 + "module": "npm/example-github-repo#feature\/branch"

597 }

598 }

599 ```

@@ -638,7 +638,7 @@ For example:

638

639 ```json

640 {

641 - "name": "ethopia-waza",

641 + "name": "@npm/ethopia-waza",

642 "description": "a delightfully fruity coffee varietal",

643 "version": "1.2.3",

644 "devDependencies": {

@@ -661,19 +661,19 @@ For example:

661

662 ```json

663 {

664 - "name": "tea-latte",

664 + "name": "@npm/tea-latte",

665 "version": "1.3.5",

666 "peerDependencies": {

667 - "tea": "2.x"

667 + "@npm/tea": "2.x"

668 }

669 }

670 ```

671

672 -This ensures your package `tea-latte` can be installed _along_ with the second major version of the host package `tea` only. `npm install tea-latte` could possibly yield the following dependency graph:

672 +This ensures your package `@npm/tea-latte` can be installed _along_ with the second major version of the host package `@npm/tea` only. `npm install tea-latte` could possibly yield the following dependency graph:

673

674 ```bash

675 -├── tea-latte@1.3.5

676 -└── tea@2.2.0

675 +├── @npm/tea-latte@1.3.5

676 +└── @npm/tea@2.2.0

677 ```

678

679 In npm versions 3 through 6, `peerDependencies` were not automatically installed, and would raise a warning if an invalid version of the peer dependency was found in the tree. As of npm v7, peerDependencies _are_ installed by default.

@@ -690,14 +690,14 @@ For example:

690

691 ```json

692 {

693 - "name": "tea-latte",

693 + "name": "@npm/tea-latte",

694 "version": "1.3.5",

695 "peerDependencies": {

696 - "tea": "2.x",

697 - "soy-milk": "1.2"

696 + "@npm/tea": "2.x",

697 + "@npm/soy-milk": "1.2"

698 },

699 "peerDependenciesMeta": {

700 - "soy-milk": {

700 + "@npm/soy-milk": {

701 "optional": true

702 }

703 }

@@ -716,13 +716,13 @@ If we define a package.json like this:

716

717 ```json

718 {

719 - "name": "awesome-web-framework",

719 + "name": "@npm/awesome-web-framework",

720 "version": "1.0.0",

721 - "bundleDependencies": ["renderized", "super-streams"]

721 + "bundleDependencies": ["@npm/renderized", "@npm/super-streams"]

722 }

723 ```

724

725 -we can obtain `awesome-web-framework-1.0.0.tgz` file by running `npm pack`. This file contains the dependencies `renderized` and `super-streams` which can be installed in a new project by executing `npm install awesome-web-framework-1.0.0.tgz`. Note that the package names do not include any versions, as that information is specified in `dependencies`.

725 +we can obtain `@npm/awesome-web-framework-1.0.0.tgz` file by running `npm pack`. This file contains the dependencies `@npm/renderized` and `@npm/super-streams` which can be installed in a new project by executing `npm install awesome-web-framework-1.0.0.tgz`. Note that the package names do not include any versions, as that information is specified in `dependencies`.

726

727 If this is spelled `"bundledDependencies"`, then that is also honored.

728

@@ -736,8 +736,8 @@ It is still your program's responsibility to handle the lack of the dependency.

736

737 ```js

738 try {

739 - var foo = require("foo");

740 - var fooVersion = require("foo/package.json").version;

739 + var foo = require("@npm/foo");

740 + var fooVersion = require("@npm/foo/package.json").version;

741 } catch (er) {

742 foo = null;

743 }

@@ -767,57 +767,57 @@ To make sure the package `foo` is always installed as version `1.0.0` no matter

767 ```json

768 {

769 "overrides": {

770 - "foo": "1.0.0"

770 + "@npm/foo": "1.0.0"

771 }

772 }

773 ```

774

775 -The above is a short hand notation, the full object form can be used to allow overriding a package itself as well as a child of the package. This will cause `foo` to always be `1.0.0` while also making `bar` at any depth beyond `foo` also `1.0.0`:

775 +The above is a short hand notation, the full object form can be used to allow overriding a package itself as well as a child of the package. This will cause `@npm/foo` to always be `1.0.0` while also making `@npm/bar` at any depth beyond `@npm/foo` also `1.0.0`:

776

777 ```json

778 {

779 "overrides": {

780 - "foo": {

780 + "@npm/foo": {

781 ".": "1.0.0",

782 - "bar": "1.0.0"

782 + "@npm/bar": "1.0.0"

783 }

784 }

785 }

786 ```

787

788 -To only override `foo` to be `1.0.0` when it's a child (or grandchild, or great grandchild, etc) of the package `bar`:

788 +To only override `@npm/foo` to be `1.0.0` when it's a child (or grandchild, or great grandchild, etc) of the package `bar`:

789

790 ```json

791 {

792 "overrides": {

793 - "bar": {

794 - "foo": "1.0.0"

793 + "@npm/bar": {

794 + "@npm/foo": "1.0.0"

795 }

796 }

797 }

798 ```

799

800 -Keys can be nested to any arbitrary length. To override `foo` only when it's a child of `bar` and only when `bar` is a child of `baz`:

800 +Keys can be nested to any arbitrary length. To override `@npm/foo` only when it's a child of `@npm/bar` and only when `@npm/bar` is a child of `@npm/baz`:

801

802 ```json

803 {

804 "overrides": {

805 - "baz": {

806 - "bar": {

807 - "foo": "1.0.0"

805 + "@npm/baz": {

806 + "@npm/bar": {

807 + "@npm/foo": "1.0.0"

808 }

809 }

810 }

811 }

812 ```

813

814 -The key of an override can also include a version, or range of versions. To override `foo` to `1.0.0`, but only when it's a child of `bar@2.0.0`:

814 +The key of an override can also include a version, or range of versions. To override `@npm/foo` to `1.0.0`, but only when it's a child of `@npm/bar@2.0.0`:

815

816 ```json

817 {

818 "overrides": {

819 - "bar@2.0.0": {

820 - "foo": "1.0.0"

819 + "@npm/bar@2.0.0": {

820 + "@npm/foo": "1.0.0"

821 }

822 }

823 }

@@ -828,7 +828,7 @@ You may not set an override for a package that you directly depend on unless bot

828 ```json

829 {

830 "dependencies": {

831 - "foo": "^1.0.0"

831 + "@npm/foo": "^1.0.0"

832 },

833 "overrides": {

834 // BAD, will throw an EOVERRIDE error

@@ -836,9 +836,9 @@ You may not set an override for a package that you directly depend on unless bot

836 // GOOD, specs match so override is allowed

837 // "foo": "^1.0.0"

838 // BEST, the override is defined as a reference to the dependency

839 - "foo": "$foo",

839 + "@npm/foo": "$foo",

840 // the referenced package does not need to match the overridden one

841 - "bar": "$foo"

841 + "@npm/bar": "$foo"

842 }

843 }

844 ```

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

+41

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

15 - /using-npm/changelog

16 ---

18 +## [11.1.0](https://github.com/npm/cli/compare/v11.0.0...v11.1.0) (2025-01-29)

19 +

20 +### Features

21 +

22 +- [`7f6c997`](https://github.com/npm/cli/commit/7f6c9973dc9a4dfebd76e52e060a9d8496b8bd98) [#8009](https://github.com/npm/cli/pull/8009) add dry-run to deprecate/undeprecate commands (@wraithgar)

23 +- [`1764a37`](https://github.com/npm/cli/commit/1764a37f1913b6a0811a85d89e029fc1dc79da54) [#8009](https://github.com/npm/cli/pull/8009) add npm undeprecate command (@wraithgar)

24 +

25 +### Bug Fixes

26 +

27 +- [`31455b2`](https://github.com/npm/cli/commit/31455b2e177b721292f3382726e3f5f3f2963b1d) [#8054](https://github.com/npm/cli/pull/8054) publish: honor force for no dist tag and registry version check (#8054) (@reggi)

28 +- [`dc31c1b`](https://github.com/npm/cli/commit/dc31c1bdc6658ab69554adcf2988ee99a615c409) [#8038](https://github.com/npm/cli/pull/8038) remove max-len linting bypasses (@wraithgar)

29 +- [`8a911ff`](https://github.com/npm/cli/commit/8a911ff895967678aa786595db3418fc28e6966a) [#8038](https://github.com/npm/cli/pull/8038) publish: disregard deprecated versions when calculating highest version (@wraithgar)

30 +- [`7f72944`](https://github.com/npm/cli/commit/7f72944e43f009cf4d55ff4fe24c459e07f588fd) [#8038](https://github.com/npm/cli/pull/8038) publish: accept publishConfig.tag to override highes semver check (@wraithgar)

31 +- [`ab9ddc0`](https://github.com/npm/cli/commit/ab9ddc0413374fbf4879da535f82e03bc4e62cf3) [#7992](https://github.com/npm/cli/pull/7992) sbom: deduplicate sbom dependencies (#7992) (@bdehamer)

32 +- [`f7da341`](https://github.com/npm/cli/commit/f7da341322c2f860156e8144b208583596504479) [#7980](https://github.com/npm/cli/pull/7980) search: properly display multiple search terms (#7980) (@wraithgar)

33 +

34 +### Documentation

35 +

36 +- [`3644e79`](https://github.com/npm/cli/commit/3644e79a73e511bc54d857bc2026b071fe18a6fe) [#8055](https://github.com/npm/cli/pull/8055) update readme for Node.js versions, remove badges (#8055) (@wraithgar)

37 +- [`f1af61f`](https://github.com/npm/cli/commit/f1af61f917e58a0a45d2b15d1e5600988b2c824f) [#8041](https://github.com/npm/cli/pull/8041) fix typos in "package-json" (#8041) (@maxkoryukov)

38 +- [`e90c6fe`](https://github.com/npm/cli/commit/e90c6feeacdf9ad010d4d73b65d7dd7d3b86efe2) [#8051](https://github.com/npm/cli/pull/8051) depth flag default value (#8051) (@milaninfy)

39 +- [`866b5ee`](https://github.com/npm/cli/commit/866b5ee3ae5ed508ecbe832d01f5ebd6b00f6789) [#8030](https://github.com/npm/cli/pull/8030) safer documentation urls, repos, packages (#8030) (@reggi)

40 +

41 +### Dependencies

42 +

43 +- [`7ddfbad`](https://github.com/npm/cli/commit/7ddfbadd1d51d07e68afbe1b91a36106d98c7bea) [#8053](https://github.com/npm/cli/pull/8053) `@npmcli/package-json@6.1.1`

44 +- [`9473a86`](https://github.com/npm/cli/commit/9473a8638257297c420136009de567c131d2f299) [#8053](https://github.com/npm/cli/pull/8053) `spdx-license-ids@3.0.21`

45 +- [`a65e5ce`](https://github.com/npm/cli/commit/a65e5ceb15c4aad6bde1ffdbee7da6f685caf81e) [#8053](https://github.com/npm/cli/pull/8053) `@sigstore/protobuf-specs@0.3.3`

46 +- [`215ebe4`](https://github.com/npm/cli/commit/215ebe4d8f6c7f30d4b6a68fa11a3372c132929e) [#8053](https://github.com/npm/cli/pull/8053) `chalk@5.4.1`

47 +

48 +### Chores

49 +

50 +- [`61f00e3`](https://github.com/npm/cli/commit/61f00e3c23211d37c7980ebd6d1cf8d1dac49f18) [#8069](https://github.com/npm/cli/pull/8069) splits out smoke-tests from publish-dryrun tests (#8069) (@reggi)

51 +- [`6d0f46e`](https://github.com/npm/cli/commit/6d0f46e67e9673e8a2dc6edb92144a73f853950c) [#8058](https://github.com/npm/cli/pull/8058) stop publish smoke from check git clean (#8058) (@reggi)

52 +- [`9281ebf`](https://github.com/npm/cli/commit/9281ebf8e428d40450ad75ba61bc6f040b3bf896) [#8057](https://github.com/npm/cli/pull/8057) fix smoke tests prerelease needs separate string args (#8057) (@reggi)

53 +- [`aa202e9`](https://github.com/npm/cli/commit/aa202e9dac2f927bedcaaed4db0eef7b3415fc68) [#8056](https://github.com/npm/cli/pull/8056) smoke tests using a preid (#8056) (@reggi)

54 +- [`18e0449`](https://github.com/npm/cli/commit/18e0449ae41703a7980cee73bae69521db6fa53e) [#8053](https://github.com/npm/cli/pull/8053) dev dependency updates (@wraithgar)

55 +- [`859a71c`](https://github.com/npm/cli/commit/859a71c59ea5f91f21a8410db46585a2fc0a8126) [#8052](https://github.com/npm/cli/pull/8052) update node versions for release integration tests (#8052) (@wraithgar)

56 +- [`7e7961d`](https://github.com/npm/cli/commit/7e7961d8936e277f3dbc8e44f9e7b07daaeb36ca) [#8038](https://github.com/npm/cli/pull/8038) bump @npmcli/eslint-config to 5.1.0 (@wraithgar)

57 +- [workspace](https://github.com/npm/cli/releases/tag/config-v10.0.1): `@npmcli/config@10.0.1`

58 +

59 ## [11.0.0](https://github.com/npm/cli/compare/v11.0.0-pre.1...v11.0.0) (2024-12-16)

61 ### Documentation

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

+1 -1

@@ -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 `1`

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`.

content/nav.yml

+1 -1

@@ -1594,7 +1594,7 @@

1594 - title: Changelog

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

1596 description: Changelog notes for each version

1597 - - title: Version 11.0.0

1597 + - title: Version 11.1.0

1598 shortName: v11

1599 url: /cli/v11

1600 default: true