CLI documentation update from CI
CI User committed
Oct 5, 2021 at 02:26 UTC
c7f1f44799ae9c6af1b23fb7517c1f33316d3311
3 files changed
+19
-2
cli/v7
+1
-1
@@ -1 +1 @@
1
-Subproject commit 6ae8cbe7ed70c17b121bd9ea42f8d8af11823c18
1
+Subproject commit 04eb43f2b2a387987b61a7318908cf18f03d97e0
content/cli/v7/using-npm/scope.md
+2
-1
@@ -107,7 +107,8 @@ desired, with `npm access` or on the npmjs.com website.
107
108
Scopes can be associated with a separate registry. This allows you to
109
seamlessly use a mix of packages from the primary npm registry and one or more
110
-private registries, such as npm Enterprise.
110
+private registries, such as [GitHub Packages](https://github.com/features/packages) or the open source [Verdaccio](https://verdaccio.org)
111
+project.
112
113
You can associate a scope with a registry at login, e.g.
114
content/cli/v7/using-npm/workspaces.md
+16
@@ -184,6 +184,22 @@ npm run test --workspaces
184
185
Will run the `test` script in both `./packages/a` and `./packages/b`.
186
187
+Commands will be run in each workspace in the order they appear in your `package.json`
188
+
189
+```
190
+{
191
+ "workspaces": [ "packages/a", "packages/b" ]
192
+}
193
+```
194
+
195
+Order of run is different with:
196
+
197
+```
198
+{
199
+ "workspaces": [ "packages/b", "packages/a" ]
200
+}
201
+```
202
+
203
### Ignoring missing scripts
204
205
It is not required for all of the workspaces to implement scripts run with the `npm run` command.