@mnci/cli 4.54.1 → 4.55.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +11 -5
- package/dist/cli.js +673 -600
- package/dist/cli.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -455,6 +455,10 @@ also gets four launch configurations, one per verify target:
|
|
|
455
455
|
| `mnci: lint` | `npm run lint` |
|
|
456
456
|
| `mnci: typecheck` | `npm run typecheck` |
|
|
457
457
|
|
|
458
|
+
Every project that has a `start` script (`mnci add` of an app kind) also gets its own configuration,
|
|
459
|
+
`mnci: <project> start`, which runs `npm run <project>:start`. These sit in a separate `mnci projects` group
|
|
460
|
+
in the dropdown.
|
|
461
|
+
|
|
458
462
|
Three details are load-bearing rather than incidental:
|
|
459
463
|
|
|
460
464
|
- **`type: node-terminal`, not `node`.** `nx run-many` executes every target in a
|
|
@@ -739,11 +743,13 @@ back and carried through unchanged**. Those tasks are per-project state written
|
|
|
739
743
|
`mnci add`, not overlay-owned, so regenerating them wholesale would wipe every
|
|
740
744
|
project's build/qa/start entry on upgrade.
|
|
741
745
|
|
|
742
|
-
The `launch` array is handled differently again — **merged, not carried through**.
|
|
743
|
-
|
|
744
|
-
|
|
745
|
-
|
|
746
|
-
|
|
746
|
+
The `launch` array is handled differently again — **merged by exact name, not carried through**.
|
|
747
|
+
The overlay replaces only the four workspace-level configurations it owns (`mnci: build`, `test`, `lint`,
|
|
748
|
+
`typecheck`); `mnci add` replaces only its own project's `mnci: <project> start`. Everything else survives an
|
|
749
|
+
upgrade: configurations you wrote, and the entries of every other project. (Matching on the `mnci: ` prefix
|
|
750
|
+
instead deleted the per-project entries on every upgrade.) The asymmetry with tasks is that the four
|
|
751
|
+
workspace-level entries are entirely overlay-authored and should track an upgrade, whereas per-project state is
|
|
752
|
+
written by `mnci add`, which the overlay cannot see.
|
|
747
753
|
|
|
748
754
|
`upgrade` also **deletes** things, which is stronger than the overwriting it
|
|
749
755
|
has always done — one more reason to run `git diff` first, as the command's own
|