Command line tools are always useful. They can help you do stuff faster and be more productive. And with Node.js it’s really easy to create them yourself.
The easiest command line tool may be something like this:
#!/usr/bin/env node console.log(process.argv);
- The first line tells that it’s Node that should be used for this.
- The second line just outputs every argument back to you.
To make this work just type
node index.js arg1 arg2 arg3 and your console will print:
['node', '/path/to/js/file', 'arg1', 'arg2', 'arg3']
Slightly more advanced
If you want to make it even more like a command line tool:
- Rename it to cmdtool (without the .js ending).
- Make it executable (sudo chmod +x cmdtool)
Then we can do the same as before, only we now just need to type
./cmdtool arg1 arg2 arg3 and the result will be the same.
To make it even more fancy either put your script in
/usr/local/bin or make a symlink to it from there (
ln -s /source/cmdtool /usr/local/bin/cmdtool).
Then you can just type
cmdtool arg1 arg2 without anything extra for the real command line feel.
So now we have a working command line tool with input arguments. Now you could go on and loop through the arguments and parse them for option flags and input and everything yourself, or you could use a node.js package made for this.
Commander reporting for duty
I have tried a package called commander that’s really easy to setup. Here is an example:
var program = require('commander'); var chalk = require('chalk');
This code snippet actually requires two packages, commander and chalk. Chalk makes it easy to output text in different colors, like red for errors.
The first part of the code defines options and format of the command line tool.
- The usage line is a textual way to describe how the program works.
- The option lines is different options, with a short syntax, full syntax, helping text and optionally a default value.
program.parsereads input (like we did with console.log in the first example).
- Next we check if there are any arguments, and if there isn’t we show an error and print the help (usage + options).
- Next we can check for the values of the different options and use them in our script.
So there we have a working command line tool, now you can make something awesome. And also, with NPM you can publish your scripts to npmjs.org so other people (and yourself later) can install it with
npm install -g cmdtool. This will put your script in a “bin” and make it executable for you.
I haven’t tried publishing to npm yet. But you basically just type
npm publish with some arguments and stuff in your package.json file. You can read more about it here.
And if you make something cool, leave a comment!