CLI Command Wiring

To wire new CLI commands into a modular TypeScript application, you create a command file exporting an async run function, add a dynamic import and execution routing block in your entry point, and update the help text to ensure consistent user UX.

Yes, adding a CLI command requires updating both the routing logic and help text. Consistent command wiring enforces adding a routing block in cli-entry.ts for execution and corresponding help text changes so the command appears in help output.

The best way to structure command files for a pluggable CLI architecture is to place each command in a dedicated TypeScript file under a commands directory, exporting a single async run function that accepts the current working directory and options.

You validate command wiring by ensuring both the command file and the routing block exist and are connected correctly. Proper wiring requires the command file to be dynamically imported and executed within the main entry point function.

Yes, you can use dynamic imports to route commands in a Node.js CLI tool. The routing block inside the main entry function dynamically imports the command file and executes its exported async run function to process user input.

Your newly added CLI command does not show up in the help output because the help text in the entry point was not updated. Consistent command wiring requires corresponding help text changes to list the new command and its usage alongside the routing block.