CLI documentation update from CI
CI User committed
Jun 18, 2021 at 02:31 UTC
7c1618835800a04e8b778fb4d82fc2ddffe23bd8
5 files changed
+44
-26
cli/v7
+1
-1
@@ -1 +1 @@
1
-Subproject commit 3f202cd777897d2213820fb00a4e85f440f69701
1
+Subproject commit 5ae068ae57d309b2ab4bc3f34c27cd1d86bcd7b2
content/cli/v7/commands/npm-audit.md
+8
-2
@@ -260,8 +260,14 @@ Not supported by all npm commands.
260
* Default: false
261
* Type: Boolean
262
263
-If set to true, it will update only the `package-lock.json`, instead of
264
-checking `node_modules` and downloading dependencies.
263
+If set to true, the current operation will only use the `package-lock.json`,
264
+ignoring `node_modules`.
265
+
266
+For `update` this means only the `package-lock.json` will be updated,
267
+instead of checking `node_modules` and downloading dependencies.
268
+
269
+For `list` this means the output will be based on the tree described by the
270
+`package-lock.json`, rather than the contents of `node_modules`.
271
272
#### `omit`
273
content/cli/v7/commands/npm-ls.md
+12
-9
@@ -165,18 +165,21 @@ variable will be set to `'production'` for all lifecycle scripts.
165
* Default: false
166
* Type: Boolean
167
168
-If true, then local installs will link if there is a suitable globally
169
-installed package.
168
+Used with `npm ls`, limiting output to only those packages that are linked.
169
171
-Note that this means that local installs can cause things to be installed
172
-into the global space at the same time. The link is only done if one of the
173
-two conditions are met:
170
+#### `package-lock-only`
171
175
-* The package is not already installed globally, or
176
-* the globally installed version is identical to the version that is being
177
- installed locally.
172
+* Default: false
173
+* Type: Boolean
174
+
175
+If set to true, the current operation will only use the `package-lock.json`,
176
+ignoring `node_modules`.
177
+
178
+For `update` this means only the `package-lock.json` will be updated,
179
+instead of checking `node_modules` and downloading dependencies.
180
179
-When used with `npm ls`, only show packages that are linked.
181
+For `list` this means the output will be based on the tree described by the
182
+`package-lock.json`, rather than the contents of `node_modules`.
183
184
#### `unicode`
185
content/cli/v7/commands/npm-pack.md
+7
@@ -46,6 +46,13 @@ Whether or not to output JSON data, rather than the normal output.
46
47
Not supported by all npm commands.
48
49
+#### `pack-destination`
50
+
51
+* Default: "."
52
+* Type: String
53
+
54
+Directory in which `npm pack` will save tarballs.
55
+
56
#### `workspace`
57
58
* Default:
content/cli/v7/using-npm/config.md
+16
-14
@@ -751,18 +751,7 @@ Use of `legacy-peer-deps` is not recommended, as it will not enforce the
751
* Default: false
752
* Type: Boolean
753
754
-If true, then local installs will link if there is a suitable globally
755
-installed package.
756
-
757
-Note that this means that local installs can cause things to be installed
758
-into the global space at the same time. The link is only done if one of the
759
-two conditions are met:
760
-
761
-* The package is not already installed globally, or
762
-* the globally installed version is identical to the version that is being
763
- installed locally.
764
-
765
-When used with `npm ls`, only show packages that are linked.
754
+Used with `npm ls`, limiting output to only those packages that are linked.
755
756
#### `local-address`
757
@@ -886,6 +875,13 @@ when publishing or changing package permissions with `npm access`.
875
If not set, and a registry response fails with a challenge for a one-time
876
password, npm will prompt on the command line for one.
877
878
+#### `pack-destination`
879
+
880
+* Default: "."
881
+* Type: String
882
+
883
+Directory in which `npm pack` will save tarballs.
884
+
885
#### `package`
886
887
* Default:
@@ -910,8 +906,14 @@ package-locks disabled use `npm prune`.
906
* Default: false
907
* Type: Boolean
908
913
-If set to true, it will update only the `package-lock.json`, instead of
914
-checking `node_modules` and downloading dependencies.
909
+If set to true, the current operation will only use the `package-lock.json`,
910
+ignoring `node_modules`.
911
+
912
+For `update` this means only the `package-lock.json` will be updated,
913
+instead of checking `node_modules` and downloading dependencies.
914
+
915
+For `list` this means the output will be based on the tree described by the
916
+`package-lock.json`, rather than the contents of `node_modules`.
917
918
#### `parseable`
919