@nexusbloom/cli 0.8.0 → 0.9.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nexusbloom/cli",
-  "version": "0.8.0",
+  "version": "0.9.0",
   "description": "NexusBloom CLI — run tools and workflows from your terminal",
   "type": "module",
   "bin": {
@@ -30,4 +30,4 @@
     "test:watch": "node --test --watch --import ./test/setup.mjs test/*.test.js",
     "lint": "node --check src/index.js"
   }
-}
+}

package/src/index.js

@@ -40,7 +40,7 @@ import {
   fetchTools, fetchToolSource, resolveToolSlug,
   generateAbbreviations, normalizeSlug, readStdin,
 } from "./tools.js";
-import { runLocal, runRemote, buildInputBody, runInteractive, reportError } from "./run.js";
+import { runLocal, runRemote, buildInputBody, runInteractive, runInteractiveFor, isExitPromptError, reportError } from "./run.js";
 import listAction from "./list.js";
 import { pipeAction, listTransforms, doctorAction } from "./commands.js";
 import { buildWizard } from "./wizard.js";
@@ -167,6 +167,21 @@ program
     const body = await buildInputBody(opts, args);
     if (body === null) return;
 
+    // ── No input at all: configure the tool interactively ──
+    // `nxb run text-statistics` with nothing to send used to fail schema
+    // validation ("Missing required fields: text"), which is a dead end for a
+    // human at a terminal. Ask for the fields instead. Only when the body is
+    // genuinely empty: any explicit input (--input/--file, key=value, piped
+    // stdin) means the caller is scripting, and a prompt there would hang CI.
+    if (Object.keys(body).length === 0 && isInteractive()) {
+      return await runInteractiveFor(resolved, {
+        json: jsonMode,
+        tools: allTools,
+        local: Boolean(opts.local),
+        key: opts.key,
+      });
+    }
+
     // ── Local vs remote ──
     if (opts.local || (!opts.key && !process.env.NEXUSBLOOM_API_KEY && !configGet("apiKey") && !configGet("key"))) {
       return await runLocal(resolved, body, { jsonMode, slugResolved: true });
@@ -710,4 +725,11 @@ function renderToolInfo(manifest, resolved) {
   console.log();
 }
 
-program.parse(process.argv);
+// `parse` does not await the async action handlers, so a Ctrl+C inside an
+// inquirer prompt surfaces here as a rejected promise rather than a thrown
+// error. Catching it turns a stack trace into a clean, conventional exit.
+program.parseAsync(process.argv).catch((err) => {
+  if (!isExitPromptError(err)) throw err;
+  process.stderr.write("\n  Cancelled.\n");
+  process.exit(130);
+});

package/src/run.js

@@ -200,6 +200,21 @@ export async function runLocal(slug, input, { jsonMode, slugResolved, quiet } =
   return { ok: true, result: res.result, durationMs: res.durationMs };
 }
 
+/**
+ * True when an error is inquirer's "the user pressed Ctrl+C" signal.
+ *
+ * @inquirer/core rejects with an `ExitPromptError` from inside a readline
+ * `SIGINT` handler. Because the CLI parses with `program.parse()` — which does
+ * not await the async action handlers — that rejection used to escape as an
+ * unhandled rejection and dump an inquirer stack trace over the user's
+ * terminal. The class is not exported from `@inquirer/prompts`, and importing
+ * `@inquirer/core` directly would tie us to a transitive dependency, so it is
+ * matched by name.
+ */
+export function isExitPromptError(err) {
+  return Boolean(err) && err.name === "ExitPromptError";
+}
+
 /** Print an error on stderr (or as JSON) and set a non-zero exit code. */
 export function reportError(jsonMode, message) {
   if (jsonMode) {
@@ -365,15 +380,30 @@ export async function runInteractive(opts = {}) {
   const selected = await promptSelect("Choose a tool:", choices, { pageSize: 15 });
   if (!selected) return;
 
-  const slug = selected.slug;
-  const resolved = await resolveToolSlug(slug, tools);
+  return await runInteractiveFor(selected.slug, { ...opts, json: jsonMode, tools });
+}
+
+/**
+ * Interactive configuration for a slug that is already known.
+ *
+ * Shared by the tool picker above and by `nxb run <slug>` with no input of any
+ * kind: a bare `nxb run text-statistics` has nothing to send, so asking for the
+ * fields is the useful behaviour rather than failing schema validation with
+ * "Missing required fields: text".
+ *
+ * Returns the executed slug, or undefined when the user backs out or the tool
+ * has no schema to configure.
+ */
+export async function runInteractiveFor(slug, opts = {}) {
+  const { json: jsonMode, tools: knownTools } = opts;
+  const resolved = await resolveToolSlug(slug, knownTools);
 
   // 2. Fetch manifest / schema
   const toolInfo = await fetchToolSource(resolved);
   if (!toolInfo?.manifest) {
     console.log(chalk.yellow(`  No schema available for "${resolved}". Falling back to raw input.`));
     await runCommand(resolved, {}, { ...opts, json: jsonMode });
-    return;
+    return resolved;
   }
 
   const { manifest } = toolInfo;
@@ -419,10 +449,11 @@ export async function runInteractive(opts = {}) {
   if (!runIt) {
     console.log(chalk.dim("  Command copied to clipboard (if available):"));
     console.log(chalk.gray(`  ${fullCommand}`));
-    return;
+    return resolved;
   }
 
   await runCommand(resolved, body, { ...opts, json: jsonMode, resolved });
+  return resolved;
 }
 
 /** Prompt for a single schema field based on its type. */