@feigi/fleet-ctl 3.24.24 → 3.24.26
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/package.json +1 -1
- package/scripts/arg.mjs +12 -9
package/package.json
CHANGED
package/scripts/arg.mjs
CHANGED
|
@@ -47,15 +47,18 @@
|
|
|
47
47
|
// scripts/*.mjs | grep -v test | grep -v defineFlags` leaves the
|
|
48
48
|
// rows that hold their own. Anchoring on `^import` is load-bearing for the
|
|
49
49
|
// same reason it is on the die() grep: unanchored, this very comment matches
|
|
50
|
-
// itself. Requiring makeDie
|
|
51
|
-
//
|
|
52
|
-
//
|
|
53
|
-
//
|
|
54
|
-
//
|
|
55
|
-
//
|
|
56
|
-
//
|
|
57
|
-
//
|
|
58
|
-
//
|
|
50
|
+
// itself. Requiring makeDie keeps the rows to scripts that refuse through a
|
|
51
|
+
// die() bound from here, and that is not every script importing this file.
|
|
52
|
+
// recipe-prove.mjs imports isDigits alone, yet it has a command line: its own
|
|
53
|
+
// parseArgs refuses an unknown flag by throwing its own usage refusal, so it
|
|
54
|
+
// holds a refusal of its own and this grep drops it. review-core.mjs binds
|
|
55
|
+
// no die() either and has no command line at all — it is imported by
|
|
56
|
+
// review-eval.mjs, and joined the `scripts/*.mjs` glob when it was renamed
|
|
57
|
+
// from `.js`. That is the price of the filter, named here rather than
|
|
58
|
+
// hidden: a test runs every importer the filter drops, and one that refuses
|
|
59
|
+
// its command line must be named in this header. Read the grep's output, plus
|
|
60
|
+
// the scripts named here, for the roster — the scripts this header names
|
|
61
|
+
// exemplify a way of qualifying, and were never the whole of it.
|
|
59
62
|
//
|
|
60
63
|
// fleet-tick.mjs is the one script still outside arg()/has(), and
|
|
61
64
|
// deliberately: it parses its flags with node:util's parseArgs, so its
|