nodejs-cli-apps-best-practices VS yargs

This article is inspired by this awesome GitHub repository created by @lirantal, please go ahead and have a look it's worth.

Indeed! I'm co-maintaining blessed-contrib and https://github.com/lirantal/nodejs-cli-apps-best-practices :-)

Mine are: an article - https://blog.developer.atlassian.com/10-design-principles-for-delightful-clis/ node cli apps best practices - https://github.com/lirantal/nodejs-cli-apps-best-practices

I also maintain the Node.js CLI Apps Best Practices repository here: https://github.com/lirantal/nodejs-cli-apps-best-practices with over 2k stars 🌟

Your tool now automates project setup, but there's room for improvement. Consider adding more features or handling user input to customize the project structure. Explore packages like yargs for parsing command-line arguments. You can learn more about yargs through their official documentation here.

This code snippet uses yargs, a Node.js package, to parse command-line arguments in a POSIX-compliant way, including support for short and long-form options. You could also use the popular commander defined as a complete node.js command-line interface.

This feature was implemented by adding a new argument option -l or --lang in yargs as below.

Creating CLIs with yargs is a piece of cake. For LZ4 there is a streaming implementation on npm which is a single function and also happened to decompress my files without any errors. Everything else is out-of-box Node.js.

Backend is more tricky. - RESTful APIs I prefer Koajs - For a RPC/microsevice, I have only used gRPC - For a CLI, yargs and inquirer

To accomplish this task, I added a new option using the yargs module. This allows me to read whatever the user inputs after using -l/--l. Following this, I added a conditional statement that defaults to en-CA whenever a language code is not inputted.

You can build them from scratch, or use one of many specialized libraries on NPM, like commander, yargs, blessed, terminal kit, prompts, and many more.