As a polyglot myself, I do admit that NodeJS is not a perfect choice to build a CLI tool. The critical point lies in empowerment.
There are many front-end developers who may not be as familiar as you with languages like c, c++, rust, or go. But due to their rich experience in JavaScript, they can master NodeJS quicker than any other language. And this post can help them build a CLI tool with less effort.
And supposing you are going to publish an NPM package which you want to bundle a binary in, will you choose to write that binary in another language, or just use NodeJS?
In addition, commander.js has no external dependencies and is well tested. Its github repo has 13,000+ stars, and it has been downloaded 70M+ times in the past month. The other packages used in this post are all optional.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
As a polyglot myself, I do admit that NodeJS is not a perfect choice to build a CLI tool. The critical point lies in empowerment.
There are many front-end developers who may not be as familiar as you with languages like
c,c++,rust, orgo. But due to their rich experience in JavaScript, they can master NodeJS quicker than any other language. And this post can help them build a CLI tool with less effort.And supposing you are going to publish an NPM package which you want to bundle a binary in, will you choose to write that binary in another language, or just use NodeJS?
In addition,
commander.jshas no external dependencies and is well tested. Its github repo has 13,000+ stars, and it has been downloaded 70M+ times in the past month. The other packages used in this post are all optional.