Node.js commandline/terminal interface.
Easily run simple or sophisticated console/terminal command(s) from Node. Supports sequential and parallel execution. Returns a promise that resolves to an array of exit codes for each command run.
With node-run-cmd you can execute a single command or an array of commands quite simply.
If you want, set in-depth options for commands being run, including callbacks for data, errors, and completion. Also set working directory, environment variables, run execution process in detached mode, set the uid and gid for the execution process(es), and set the shell to run the command in.
The source that this package is based on has been in production since February, 2016. Note that the examples here are for illustrative purposes only; most of the time there is no real need to run commands from Node, and they should be avoided if there are cross-platform requirements. This package aims to help when there isn't an agreeable alternative.
If most of your commands are filesystem related, I would instead look to node-fs-extra to accomplish what the commands would have.
Licensed via MIT License.
The quickest way to get started is to run a single, simple command, then increase complexity as needed.
Install the package:
$ npm install --save node-run-cmd
Use the package:
var nrc = ;nrc;
These examples get increasingly complex to demonstrate the robustness of the package. Not all options are demonstrated; see the Options Object section for all possible options.
var commands ='mkdir foo''touch foo/bar.txt';var options = cwd: 'path/to/my/dir' ;nrc;
var commands =command: 'mkdir foo' cwd: 'dir1'command: 'mkdir foo' cwd: 'dir2';nrc;
var commands ='mkdir foo'command: 'mkdir foo' cwd: 'different/dir''mkdir bar';var options = cwd: 'default/dir' ;nrc;
var commands ='./runCompute1.sh''./runCompute2.sh''./runCompute3.sh';var options = mode: 'parallel' ;nrc;
var promise = nrc.run(commands, globalOptions);
A promise that resolves to an array of exit codes for commands run.
commands can be specified in any one of the below formats
|commands||string||yes||The command to run||
|commands||array(string)||yes||An array of string commands to run||
|commands||array(object)||yes||An array of objects describing commands to run. See section Options Object for allowed properties.||
|commands||array(object or string)||yes||A mixed array of objects describing commands and string commands to run. See section Options Object for allowed properties.||
|globalOptions||object||no||The global options to set for each command being run. Overridden by command's options.||
Options available for the
|command||string||yes||-||the command to run|
||the directory to run the command in|
|onData||function(data)||no||null||where to send output from stdout. Called each time stdout is written.|
|onError||function(data)||no||null||where to send output from stderr. Called each time stderr is written.|
|onDone||function(code)||no||null||where to send the exit code of the command. Called once.|
||show verbose output|
||what function to use to log when verbose is set to true|
|env||object||no||null||Environment key-value pairs|
|stdio||string or array||no||null||Child's stdio configuration|
|detached||boolean||no||null||Prepare child to run independently of its parent process. Specific behavior depends on the platform.|
|uid||number||no||null||Sets the user identity of the process.|
|gid||number||no||null||Sets the group identity of the process.|
|shell||boolean or string||no||null||If true, runs command inside of a shell. Uses '/bin/sh' on UNIX, and 'cmd.exe' on Windows. A different shell can be specified as a string. The shell should understand the -c switch on UNIX, or /s /c on Windows. Defaults to false (no shell).|
These options can only be set in the
||Whether to run commands in series (sequentially) or in parallel.|