Registry / http-networking / node-run-cmd

node-run-cmd

JSON →
library1.0.1jsnpmunverified

node-run-cmd is a Node.js package designed to execute console or terminal commands programmatically. It supports both single and multiple commands, with options for sequential or parallel execution. The current stable version is 1.0.1, marking its initial public release. It offers robust control over command execution, including setting working directories, environment variables, detached mode, and callbacks for data, errors, and completion. It returns promises for asynchronous handling and also supports a callback style. Key differentiators include its detailed options object for fine-grained control over child processes and the ability to define different working directories for individual commands within an array. The package explicitly cautions against its use for cross-platform applications or when `node-fs-extra` can accomplish filesystem-related tasks more effectively, positioning itself as a solution for specific, platform-dependent command execution needs.

http-networkingdevops
npm install node-run-cmd
github ↗package ↗
INSTALL
IMPORT
SIG · NODE-RUN-CMD
N
node-run-cmd
http-networkingjavascriptv1.0.1
Install
—
Import
—
Disk
—
Pass rate
0/ 6
Env Coverage0 / 6
glibc
18–22
musl
18–22
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18–226 runs
build_error
glibc
node 18–226 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

nrc
✓ const nrc = require('node-run-cmd');
✗ import { run } from 'node-run-cmd';
This package is primarily designed for CommonJS (`require`) usage in Node.js environments. While ESM import might work with specific loader configurations, the documented and intended usage is via `require`. The module exports a single object containing the `run` method.

Demonstrates installing the package, running multiple shell commands with options, and handling promise-based success and error states, including a basic cleanup.

const nrc = require('node-run-cmd'); // Run multiple commands sequentially, setting a specific working directory for one of them, // and handle both successful completion and errors using promises. nrc.run([ 'mkdir my-temp-dir', { command: 'echo "Hello, world!" > message.txt', cwd: 'my-temp-dir' }, 'ls my-temp-dir' ]).then(function(exitCodes) { console.log('All commands finished successfully with exit codes:', exitCodes); // Clean up return nrc.run('rm -rf my-temp-dir'); }).then(() => { console.log('Cleanup successful.'); }).catch(function(err) { console.error('One or more commands failed:', err); // Attempt cleanup even if a command failed nrc.run('rm -rf my-temp-dir').catch(cleanupErr => console.error('Cleanup also failed:', cleanupErr)); });
Debug
Known issues
gotchaThe package explicitly warns against using it for applications requiring cross-platform compatibility, as shell commands are inherently platform-specific.
fix
If cross-platform compatibility is a requirement, consider using platform-agnostic Node.js APIs (e.g., `fs` module) or libraries like `node-fs-extra` for file system operations, or abstracting commands based on `process.platform`.
affects: >=1.0.0
gotchaIt is not recommended for filesystem-related tasks if `node-fs-extra` can achieve the same result, as `node-fs-extra` provides a more robust and cross-platform compatible API.
fix
For common file system operations (e.g., creating/deleting directories or files), prefer using `node-fs-extra` to leverage its native Node.js APIs and cross-platform reliability.
affects: >=1.0.0
gotchaIncorrect handling of shell-specific syntax, quoting, or command paths can lead to unexpected behavior or failures.
fix
Be meticulous about command string construction, especially with paths and arguments containing spaces or special characters. Use proper escaping (e.g., backticks, double quotes) according to the target shell. For robustness, consider passing command arguments as an array if the underlying `child_process` API allows.
affects: >=1.0.0
Errors
Common errors & fixes
Error: spawn <command> ENOENT
The command specified does not exist in the system's PATH, or the provided path to the executable is incorrect.
fix
Verify that the command (`<command>`) is installed and available in the system's PATH. If not, provide the full absolute path to the executable or ensure it's installed globally or within `node_modules/.bin` if applicable.
Command failed to run with error: Error: Command failed: <command> ...
The executed shell command returned a non-zero exit code, indicating an error during its execution.
fix
Inspect the `stderr` output (available via the `onError` callback or within the error object of the promise rejection) to diagnose the specific issue with the command. This often relates to incorrect arguments, file permissions, or environmental issues for the command itself.
TypeError: nrc.run is not a function
This error occurs when `nrc` is undefined or does not have a `run` method, typically due to an incorrect or missing `require('node-run-cmd')` statement.
fix
Ensure that `const nrc = require('node-run-cmd');` is correctly placed and executed before attempting to call `nrc.run(...)`. Verify the package is installed in `node_modules`.
Upgrade
Version history
1.0.1latest on npm
Audit
Dependencies

No dependency data recorded yet.

Agent activity
2 hits · last 30 days
node
2
Resources
githubhttps://github.com/c-h-/node-run-cmd ↗
packagehttps://www.npmjs.com/package/node-run-cmd ↗
node-run-cmd — npm install node-run-cmd · libregistry