KickJS Custom CLI Commands for Seeding, Resetting, and Testing
The article discusses how the author moved all operational commands for their Jira-like task management backend built on KickJS into the framework's configuration file, allowing for discoverable, documented, and composable CLI commands without the need for extra dependencies.
Why it matters
Streamlining operational commands can improve developer productivity and project maintainability.
Key Points
- 1Moved all operational commands into the KickJS config file
- 2Allows for CLI commands like 'kick seed', 'kick db:reset', 'kick check'
- 3No extra CLI framework, commander.js, or yargs required
- 4CLI-level commands provide better developer experience than npm scripts
Details
The author explains that as projects accumulate scripts, the package.json file can become cluttered with many commands that are difficult to remember and maintain. For their Vibed project, they moved all operational commands into the KickJS framework's configuration file, 'kick.config.ts'. This allows them to define custom commands with descriptive names and steps, which can then be executed using the 'kick' binary. The author argues that this approach provides a better developer experience than relying on npm scripts, as the commands are centralized, documented, and composable.
No comments yet
Be the first to comment