Add shell completion support via a 'completion' subcommand for bash, zsh, and fish. Generic pattern for any Commander.js CLI, with static and dynamic completion examples.
The English summary is being prepared. Showing the original description.
Add --json flag to CLI commands for machine-readable output on stdout. Generic pattern for any CLI tool, enabling piping to jq and CI/CD integration while keeping human-readable output on stderr.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Add --json flag to commands that produce output, writing structured JSON to stdout for programmatic consumption.
--json is passed)This allows: mycli show --json | jq '.items' to work while the user still sees progress on stderr.
program
.command('show')
.option('--json', 'Output in JSON format')
.action(async (options) => {
const result = await buildResult()
if (options.json) {
process.stdout.write(JSON.stringify(result, null, 2) + '\n')
} else {
displayHumanReadable(result)
}
})
Define typed interfaces for each command's JSON output:
interface ShowResult {
items: Array<{
name: string
status: string
// ... domain-specific fields
}>
}
When --json is active, suppress spinners and progress bars on stderr:
if (options.json) {
logger.setLevel('warn') // Only show warnings and errors
}
On error with --json, still output JSON to stdout:
if (options.json) {
process.stdout.write(
JSON.stringify(
{
success: false,
error: {
type: error.name,
message: error.message,
exitCode: error instanceof AppError ? error.exitCode : 1,
},
},
null,
2,
) + '\n',
)
}
process.exit(exitCode)
test('show --json outputs valid JSON to stdout', async () => {
const { stdout, stderr } = await runCli(['show', '--json'])
const result = JSON.parse(stdout)
expect(result.items).toBeInstanceOf(Array)
// stderr may still have log output
})
Add --json to any command that displays data:
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add shell completion support via a 'completion' subcommand for bash, zsh, and fish. Generic pattern for any Commander.js CLI, with static and dynamic completion examples.
The English summary is being prepared. Showing the original description.
Add zod schema validation for CLI options and YAML/JSON config files. Generic pattern for runtime validation with type-safe parsing and clear error messages in any Commander.js CLI.
The English summary is being prepared. Showing the original description.
Set up @changesets/cli for semantic versioning, CHANGELOG generation, and npm publishing in a monorepo or single package. Covers init, config, contributor workflow, GitHub Actions release automation, and npm provenance.
The English summary is being prepared. Showing the original description.
Add automatic CI/CD environment detection using ci-info package. Generic pattern for any CLI tool that needs to adapt behavior (prompts, output, integrations) based on whether it's running in CI.
The English summary is being prepared. Showing the original description.
Polish CLI user experience with @clack/prompts for interactive flows, update-notifier for version awareness, and enhanced Commander.js help text with examples and colors. Generic patterns for any Node.js CLI.
The English summary is being prepared. Showing the original description.
Implement a structured error class hierarchy with actionable messages, proper exit codes, debug mode via env var, and bug report hints on unexpected errors. Generic pattern for any CLI tool or Node.js application.
The English summary is being prepared. Showing the original description.