Skip to main content

Troubleshooting

Module not initialized​

Make sure @quik/cli is registered in your bootstrap module. Its setup hook registers the built-in commands, and onBeforeInit builds the yargs instance from whatever is registered in CommandStore at that point — custom commands must be registered before onBeforeInit runs.

quik <command> prints "Unknown argument" or fails strict validation​

The CLI runs yargs with .strict() and .demandCommand(1), so unregistered options or a missing command name cause a hard failure with usage help, not a silent no-op.

A custom command isn't recognized​

Commands must be registered with CommandStore.register(...) before the CLI builds its yargs instance (onBeforeInit). Registering a class after that point (e.g. from a module loaded later in the bootstrap order) will not show up in --help or be runnable.

Running a command by name throws​

CommandStore.get(name) / CommandStore.execute(name, args) throw MissingCommandError when no command with that name was registered.

Common Errors​

  • quik.errors.cli.missing-command: CommandStore.get/execute was called with a command name that isn't registered.