CLI documentation update from CI
npm CLI robot committed
Aug 17, 2022 at 03:12 UTC
0f0fe7e64bf006c4cb889a13746aab9a73d49f70
3 files changed
+3
-3
cli/v8
+1
-1
@@ -1 +1 @@
1
-Subproject commit 9dc69830a5d78aa4042746d54e2a6b0d2af70caa
1
+Subproject commit 41d0f51c34b24659d080beff0d53905975d34213
content/cli/v8/configuring-npm/package-json.md
+1
-1
@@ -883,7 +883,7 @@ be found or fails to install, then you may put it in the
883
`optionalDependencies` object. This is a map of package name to version or
884
url, just like the `dependencies` object. The difference is that build
885
failures do not cause installation to fail. Running `npm install
886
---no-optional` will prevent these dependencies from being installed.
886
+--omit=optional` will prevent these dependencies from being installed.
887
888
It is still your program's responsibility to handle the lack of the
889
dependency. For example, something like this:
content/cli/v8/using-npm/dependency-selectors.md
+1
-1
@@ -62,7 +62,7 @@ The [`npm query`](/cli/v8/commands/npm-query) commmand exposes a new dependency
62
- [`:private`](https://docs.npmjs.com/cli/v8/configuring-npm/package-json#private) when a dependency is private
63
- `:link` when a dependency is linked (for instance, workspaces or packages manually [`linked`](https://docs.npmjs.com/cli/v8/commands/npm-link)
64
- `:deduped` when a dependency has been deduped (note that this does *not* always mean the dependency has been hoisted to the root of node_modules)
65
-- `:override` when a dependency is an override (not implemented yet)
65
+- `:overridden` when a dependency has been overridden
66
- `:extraneous` when a dependency exists but is not defined as a dependency of any node
67
- `:invalid` when a dependency version is out of its ancestors specified range
68
- `:missing` when a dependency is not found on disk