package
Cross platform child_process#spawn and child_process#spawnSync
npm install @cspotcode/cross-spawnGitHub-flavored package documentation.
Across all versions.
Download trend unavailable.
Runtime metadata.
Tagged topics.
Estimated unpacked size across 7 packages.
3.3 MB
Includes dependencies.
4 direct · 3 outdated
^1.2.9
7.0.0
^4.0.1
11.5.3
^4.2.0
4.2.0
^1.2.0
2.0.0
This is a proof-of-concept fork of cross-spawn while I wait for a fix to be merged upstream.
A cross platform solution to node's spawn and spawnSync.
$ npm install @cspotcode/cross-spawn
If you are using spawnSync on node 0.10 or older, you will also need to install spawn-sync:
$ npm install spawn-sync
Node has issues when using spawn on Windows:
options.shell support on node <v4.8del or dirAll these issues are handled correctly by cross-spawn.
There are some known modules, such as win-spawn, that try to solve this but they are either broken or provide faulty escaping of shell arguments.
Exactly the same way as node's spawn or spawnSync, so it's a drop in replacement.
var spawn = require('@cspotcode/cross-spawn');
// Spawn NPM asynchronously
var child = spawn('npm', ['list', '-g', '-depth', '0'], { stdio: 'inherit' });
// Spawn NPM synchronously
var results = spawn.sync('npm', ['list', '-g', '-depth', '0'], { stdio: 'inherit' });options.shell as an alternative to @cspotcode/cross-spawnStarting from node v4.8, spawn has a shell option that allows you run commands from within a shell. This new option solves most of the problems that @cspotcode/cross-spawn attempts to solve, but:
<v4.8If you are using the shell option to spawn a command in a cross platform way, consider using @cspotcode/cross-spawn instead. You have been warned.
While @cspotcode/cross-spawn handles shebangs on Windows, its support is limited: e.g.: it doesn't handle arguments after the path, e.g.: #!/bin/bash -e.
Remember to always test your code on Windows!
$ npm test
Released under the MIT License.