Chaining commands when using Guides

[mrleblanc101]

I'm creating a CLI using city and clack/prompts like so:

#!/usr/bin/env node
import { defineCommand, runMain } from "citty";
import { createCommand } from "./commands/create.js";
import { initCommand } from "./commands/init.js";
import { startCommand } from "./commands/start.js";
import { stopCommand } from "./commands/stop.js";
import { statusCommand } from "./commands/status.js";
import { syncCommand } from "./commands/sync.js";

const main = defineCommand({
  meta: {
    name: "kubeo-cli",
    version: "0.1.0",
    description: "Kubeo CLI",
  },
  subCommands: {
    create: createCommand,
    init: initCommand,
    start: startCommand,
    stop: stopCommand,
    status: statusCommand,
    sync: syncCommand,
  },
});

runMain(main);

I have individual command, but also a master create which prompt to run the init and sync command.
How would I handle intro/outro and guides ?
Currently, the guide are broken, and I'm wondering if i'm doing something wrong or if I need to manage this manually.

The sub-commands are called like so:

const runInit = await p.confirm({
  message: "Run init now?",
  initialValue: true,
});

if (p.isCancel(runInit) || !runInit) {
  p.outro(`Run \`cd ${name} && kubeo-cli init\` when you're ready.`);
  return;
}

spawnSync("kubeo-cli", ["init"], { stdio: "inherit" });
p.outro("Done.");

[dreyfus92]

hey @mrleblanc101, when guides look “broken” in that setup, it’s usually because of how intro / outro interact with the TTY when two separate Node processes both use Clack with stdio: 'inherit': the parent hasn’t finished its guide frame (with outro) before the child prints its own intro / prompts, so the columns and corners can overlap or misalign.

you could close the parent session before spawning, call something like p.outro('Running init...') immediately before spawnSync, so the parent's guide column finishes before kubeo-cli init prints its own intro / prompts. You can still print a final liner after the child if you want but be e aware that you might have 2 "outros", which is usually fine.

on the other hand if you want a continuous flow avoid spawning a second CLI on the same TTY for that path: call your init logic in process under a single intro / outro for the whole wizard.

[mrleblanc101]

Thanks,

If I want one single intro/outro, I would need to have logic in each command to check if they are run individually or from a "master" command.

I think I'll just switch the spawnSync and outro like so as you've said:

p.outro("Done.");
spawnSync("kubeo-cli", ["init"], { stdio: "inherit" });

I tough outro needed to be last, but I guess it just print some text so it can be anywhere.
I also tried disabling guides, but it didn't look as good.