@basaltkit/cli 1.2.1 → 1.2.3

package/README.md

@@ -209,6 +209,8 @@ A Basalt plugin that registers the commands in the `'commands'` metadata bucket,
 
 A minimal argument parser: the first "loose" word is the command; `--key=value` and `--flag` become flags. Returns `{ command: string | undefined, args: string[], flags: Record<string, string | boolean> }`.
 
+A bare `--no-<name>` is the conventional **negation**: it yields `flags['<name>'] === false`, not `flags['no-<name>'] === true`. That is what makes documented opt-outs such as `basalt dev --no-routes` take effect — commands test `flags['routes'] !== false`. Only the bare form negates: `--no-cache=x` still parses as the literal key `no-cache`.
+
 ### `consoleIo(): CommandIo`
 
 A `CommandIo` implementation that writes to the console (`console.log` / `console.error`; `table` renders via `renderTable`). It's the default for `runCli`.

package/dist/parse.d.ts

@@ -3,5 +3,14 @@ export interface ParsedArgv {
     args: string[];
     flags: Record<string, string | boolean>;
 }
-/** Minimal argv parser: first bare word is the command; `--key=value` and `--flag` become flags. */
+/**
+ * Minimal argv parser: first bare word is the command; `--key=value` and
+ * `--flag` become flags.
+ *
+ * A bare `--no-<name>` is the conventional **negation**: it sets
+ * `flags['<name>'] = false`, not `flags['no-<name>'] = true`. That is what makes
+ * documented opt-outs like `basalt dev --no-routes` actually take effect —
+ * commands test `flags['routes'] !== false`. Only the bare form negates:
+ * `--no-cache=x` still parses as the literal key `no-cache`.
+ */
 export declare function parseArgv(argv: string[]): ParsedArgv;

package/dist/parse.js

@@ -1,4 +1,13 @@
-/** Minimal argv parser: first bare word is the command; `--key=value` and `--flag` become flags. */
+/**
+ * Minimal argv parser: first bare word is the command; `--key=value` and
+ * `--flag` become flags.
+ *
+ * A bare `--no-<name>` is the conventional **negation**: it sets
+ * `flags['<name>'] = false`, not `flags['no-<name>'] = true`. That is what makes
+ * documented opt-outs like `basalt dev --no-routes` actually take effect —
+ * commands test `flags['routes'] !== false`. Only the bare form negates:
+ * `--no-cache=x` still parses as the literal key `no-cache`.
+ */
 export function parseArgv(argv) {
     let command;
     const args = [];
@@ -7,8 +16,12 @@ export function parseArgv(argv) {
         if (token.startsWith('--')) {
             const body = token.slice(2);
             const eq = body.indexOf('=');
-            if (eq === -1)
-                flags[body] = true;
+            if (eq === -1) {
+                if (body.startsWith('no-') && body.length > 3)
+                    flags[body.slice(3)] = false;
+                else
+                    flags[body] = true;
+            }
             else
                 flags[body.slice(0, eq)] = body.slice(eq + 1);
         }

package/package.json

@@ -1,9 +1,13 @@
 {
   "name": "@basaltkit/cli",
-  "version": "1.2.1",
+  "version": "1.2.3",
+  "engines": {
+    "node": ">=22.5.0"
+  },
   "description": "The 'basalt' command framework for Basalt apps: define commands, run them against a booted app, and inspect routes and schedules.",
   "license": "MIT",
   "type": "module",
+  "sideEffects": false,
   "exports": {
     ".": {
       "types": "./dist/index.d.ts",
@@ -14,7 +18,7 @@
     "dist"
   ],
   "dependencies": {
-    "@basaltkit/core": "^1.1.2"
+    "@basaltkit/core": "^1.3.1"
   },
   "devDependencies": {
     "@types/node": "^26.3.0",