mgutz/execsync

node.js' missing execSync

execsync's Issues

..

Fails to build on node 0.11.16

Causes downstream packages to fail to install on latest node 0.11.16 see ember-cli-deploy/ember-cli-deploy#31

Problems with grunt-favicons and win32

There is a problem running grunt-favions, the output states that execSync isnt compatible with the installed node, which is grunt-favicons.

The exact error is:
Loading "favicons.js" tasks...ERROR
Error: execSync incompatible with installed nodejs

Comment on issue 5.

Hi, it took me more than a couple days to reply, but I replied to issue #5. Thought I'd mention it here because I don't think we get notifications for closed issues.

no license

neither the README, nor the package.json mention a license. also, there is no LICENSE file. by default people have to assume this project is not licensed for their use at all. I'm sure that was not your intention. could you add some licensing information please? thanks!

Cannot find module './build/Release/shell'

After installing with npm install execSync I got Cannot find module './build/Release/shell' error.
I had to go into the node_modules directory and build it myself passing the flag --python python2 to the node-gyp rebuild command.

Some errors on Linux

While I already submitted a pull request regarding an issue with compiling the library, it seems other things are broken under Linux as well. The test suite fails as a whole. One issue I saw was that the following line:

cmd = '(' + command + ') &> ' + tempName;

(in index.js:38)

did not work on my system (Ubuntu 13.04, 64bit). Removing the & worked for some reason. I did not look into the C++ code, however, so I can't tell why this happens. In bash, this works as expected, but within this script, the temp file is created but not written to. Is there a particular reason for using &> instead of plain >?

There are some other bugs as well, so maybe if you get around to test the whole thing on a Linux machine, you'll be able to make more sense out of it!

Cheers!

mark package as deprecated on npm

if possible so people know it's deprecated

Installation error

I get the following error trying to install using

npm install -g execSync

[email protected] install /usr/lib/node_modules/execSync
node-gyp rebuild

Traceback (most recent call last):
File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 15, in
import gyp
File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/init.py", line 8, in
import gyp.input
File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 5, in
from compiler.ast import Const
ImportError: No module named compiler.ast
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:337:16)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:99:17)
gyp ERR! stack at Process._handle.onexit (child_process.js:678:10)
gyp ERR! System Linux 3.8.13
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/lib/node_modules/execSync
gyp ERR! node -v v0.8.22
gyp ERR! node-gyp -v v0.12.2
gyp ERR! not ok
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! sh "-c" "node-gyp rebuild" failed with 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the execSync package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls execSync
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.8.13
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "-g" "execSync"
npm ERR! cwd /home/root/beagle
npm ERR! node -v v0.8.22
npm ERR! npm -v 1.2.14
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/root/beagle/npm-debug.log
npm ERR! not ok code 0

npm install -g angular-cli fails on execSync

I get the following error executing npm install-g angular-cli on OSX el-capitan
I have installed and reinstalled the latest version of nodejs (7.0.0, fyi have also tried 6.9.1 with same results) and don't think it is a bad install.

The err on output is
...
136167 verbose stack Error: [email protected] install: node install.js
136167 verbose stack Exit status 1
136167 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
136167 verbose stack at emitTwo (events.js:106:13)
136167 verbose stack at EventEmitter.emit (events.js:191:7)
136167 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
136167 verbose stack at emitTwo (events.js:106:13)
136167 verbose stack at ChildProcess.emit (events.js:191:7)
136167 verbose stack at maybeClose (internal/child_process.js:877:16)
136167 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
136168 verbose pkgid [email protected]
136169 verbose cwd /Users/kboogert
136170 error Darwin 15.6.0
136171 error argv "/usr/local/Cellar/node/7.0.0/bin/node" "/usr/local/bin/npm" "install" "-g" "angular-cli"
136172 error node v7.0.0
136173 error npm v3.10.8
136174 error code ELIFECYCLE
136175 error [email protected] install: node install.js
136175 error Exit status 1
136176 error Failed at the [email protected] install script 'node install.js'.
136176 error Make sure you have the latest version of node.js and npm installed.
136176 error If you do, this is most likely a problem with the execSync package,
136176 error not with npm itself.
136176 error Tell the author that this fails on your system:
136176 error node install.js
136176 error You can get information on how to open an issue for this project with:
136176 error npm bugs execSync
136176 error Or if that isn't available, you can get their info via:
136176 error npm owner ls execSync
136176 error There is likely additional logging output above.
136177 verbose exit [ 1, true ]
...

npm-debug.log.zip

permissions issue when installing 1.0.1-pre on ubuntu

When it's building the program it says root doesn't have permission to access /home/slang/.node-gyp/0.10.22. I think that's where it went wrong, but that doesn't make much sense because root should be able to access everything, right?

anyway, here's the full error log:

$ sudo npm install -g execSync
npm http GET https://registry.npmjs.org/temp
npm http 304 https://registry.npmjs.org/temp
npm http GET https://registry.npmjs.org/rimraf
npm http 304 https://registry.npmjs.org/rimraf
npm http GET https://registry.npmjs.org/graceful-fs
npm http 304 https://registry.npmjs.org/graceful-fs

> [email protected] install /usr/lib/node_modules/execSync
> node-gyp rebuild

gyp WARN EACCES user "root" does not have permission to access the dev dir "/home/slang/.node-gyp/0.10.22"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/lib/node_modules/execSync/.node-gyp"
gyp http GET http://nodejs.org/dist/v0.10.22/node-v0.10.22.tar.gz
gyp http 200 http://nodejs.org/dist/v0.10.22/node-v0.10.22.tar.gz
make: Entering directory `/usr/lib/node_modules/execSync/build'
  CXX(target) Release/obj.target/shell/src/shell.o
make: g++: Command not found
make: *** [Release/obj.target/shell/src/shell.o] Error 127
make: Leaving directory `/usr/lib/node_modules/execSync/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:789:12)
gyp ERR! System Linux 3.11.0-13-generic
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/lib/node_modules/execSync
gyp ERR! node -v v0.10.22
gyp ERR! node-gyp -v v0.11.0
gyp ERR! not ok 
npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the execSync package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls execSync
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.11.0-13-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "-g" "execSync"
npm ERR! cwd /home/slang
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR! code ELIFECYCLE
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/slang/npm-debug.log
npm ERR! not ok code 0

[email protected] install: `node install.js` - fails in jenkins server

It keeps failing in jenkins server:

03:31:13 + node -v
03:31:13 v8.16.2
03:31:13 + npm -v
03:31:13 6.4.1
03:31:13 + npm i
03:31:23 npm WARN deprecated [email protected]: angular-cli has been renamed to @angular/cli. Please update your dependencies.
03:31:24 npm WARN deprecated [email protected]: Possible security and integrity issues resolved in version 0.4.0
03:31:27 npm WARN deprecated [email protected]: One of your dependencies needs to upgrade to fsevents v2: 1) Proper nodejs v10+ support 2) No more fetching binaries from AWS, smaller package size
03:31:30 npm WARN deprecated [email protected]: Please replace with usage of fs.existsSync
03:31:31 npm WARN deprecated [email protected]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
03:31:31 npm WARN deprecated [email protected]: Use uuid module instead
03:31:33 npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
03:31:33 npm WARN deprecated [email protected]: This module relies on Node.js's internals and will break at some point. Do not use it, and update to [email protected].
03:31:34 npm WARN deprecated [email protected]: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
03:31:37 npm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
03:31:46 npm WARN deprecated [email protected]: Please replace with usage of fs.existsSync
03:31:48 npm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
03:31:53 npm WARN deprecated [email protected]: This module is no longer maintained, try this instead:
03:31:53 npm WARN deprecated npm i nyc
03:31:53 npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives.
03:31:55 npm WARN deprecated [email protected]: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
03:31:55 npm WARN deprecated [email protected]: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
03:31:55 npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
03:31:55 npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
03:31:55 npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
03:31:56 npm WARN deprecated [email protected]: This module is no longer maintained, try this instead:
03:31:56 npm WARN deprecated npm i nyc
03:31:56 npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives.
03:31:56 npm WARN deprecated [email protected]: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
03:31:58 npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
03:35:10
03:35:10 > [email protected] install /Users/iosapp_test1/jenkins/workspace/ProcurementAppFinalQABuild-IOS/node_modules/chokidar/node_modules/fsevents
03:35:10 > node install
03:35:10
03:35:11
03:35:11 > [email protected] install /Users/iosapp_test1/jenkins/workspace/ProcurementAppFinalQABuild-IOS/node_modules/execSync
03:35:11 > node install.js
03:35:11
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic-native/[email protected] requires a peer of rxjs@^5.5.11 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic/[email protected] requires a peer of @angular-devkit/[email protected] - 8 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic/[email protected] requires a peer of @angular-devkit/[email protected] - 8 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic/[email protected] requires a peer of @angular/[email protected] - 8 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @ionic/[email protected] requires a peer of rxjs@>=6.2.0 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN [email protected] requires a peer of rxjs@^6.4.0 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN [email protected] requires a peer of node-sass@^3.4.2 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN [email protected] requires a peer of tslint@^3.0.0 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN @angular/[email protected] requires a peer of typescript@^2.0.2 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN [email protected] requires a peer of typescript@^2.0.0 but none is installed. You must install peer dependencies yourself.
03:35:20 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/chokidar/node_modules/fsevents):
03:35:20 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] install: node install
03:35:20 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: spawn sh ENOENT
03:35:20
03:35:20 npm ERR! file sh
03:35:20 npm ERR! path sh
03:35:20 npm ERR! code ELIFECYCLE
03:35:20 npm ERR! errno ENOENT
03:35:20 npm ERR! syscall spawn sh
03:35:20 npm ERR! [email protected] install: node install.js
03:35:20 npm ERR! spawn sh ENOENT
03:35:20 npm ERR!
03:35:20 npm ERR! Failed at the [email protected] install script.

npm install fails inside docker container

> node install.js

sh: 1: node: Permission denied
npm ERR! Linux 3.13.0-24-generic
npm ERR! argv "/root/node-v4.1.2-linux-x64/bin/node" "/root/node-v4.1.2-linux-x64/bin/npm" "install"
npm ERR! node v4.1.2
npm ERR! npm  v2.14.4
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR! [email protected] install: `node install.js`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the [email protected] install script 'node install.js'.
npm ERR! This is most likely a problem with the execSync package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node install.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls execSync
npm ERR! There is likely additional logging output above

Fails to git push origin

I'm trying to use this with grunt and when pushing to a remote git I get this error:

{ stdout: 'fatal: The remote end hung up unexpectedly\nfatal: write error: Broken pipe\n',
  code: 128 }

Using child_process.exec or exec-sync works.

Win32 possible bug

(LPSTR) command,// Command line

you can't do that with a const char* in general case because this parameter is actually being written to by windows runtime. It's better to copy the cmd line.

Warning: Module version mismatch, refusing to load on Node v.0.8.23

Hello,

using your node module on Node v.0.8.23 will exit my script with following error:

Warning: Module version mismatch, refusing to load. Use --force to continue

You don't refer to specific node versions in your package.json
"engines": {
"node": "*"
}

BR,
mybecks

writing to stdin?

My apologies if I'm missing something obvious, but I've poked around in the code and the issue list and it isn't clear to me if or how to do this.

Is there a way to provide data for the input stream being read by the process invoked by execSync.run or execSync.exec? I.e., can I provide a buffer or string, or write to the stream directly?

(A somewhat laborious work-around would be for me to write to a temp file and then cat that file as part of the command passed to exec or run, but I wonder if that is built in or could be added.)

Repository field in package.json

When running npm install, I get the annoying warning:

npm WARN package.json [email protected] No repository field.

This can be removed by adding the following to package.json:

"repository": { 
  "type": "git",
  "url": "http://github.com/mgutz/execSync.git"
}

Cannot separately process stderr

execSync redirects stderr to stdout:

sh = require('execSync');
var stdout = sh.exec('echo my_error >&2').stdout;
console.log('stdout: ' + stdout); // stdout: my_error

However, it would be preferable (IMO) if it worked like this instead:

var sh = require('execSync');
var stdout = sh.exec('echo my_output').stdout;
var stderr = sh.exec('echo my_error >&2').stderr;
console.log('stdout: ' + stdout + ' ; stderr: ' + stderr); // stdout: my_output ; stderr: my_error

Dynamic Symbol Retrieval Error:

Npm problems

Getting a 404 on your package on npm
https://www.npmjs.com/package/execSync

However I can find it in the search and npm install execSync works fine.

Odd. Perhaps publishing a new version will fix it.

Running win32 binary in Nodejs x64

We were using grunt-spawn-shell plugin, which uses the execSync plugin to run a specific command. We kept getting an error %1 is not a valid win32 application. After trying to debug for a while, we found out that the 64-bit version of Node does not work to run 32-bit DLLs.

This is fine on the face of it, but the messaging was confusing and lacking in details. There are also no mention of this in the documentation as far as I could find.

Install failing on Windows 8

The basic npm install fails.

Some callbacks to `child_process.exec` are never called

If execSync.exec is used before node's child_process.exec, the exec callback to child_process.exec is never called.

This only happens when multiple calls to execSync and child_process.exec are invoked one after the other.

Example script to demonstrate the issue:

 var exec = require('child_process').exec,
     execSync = require('execSync');

 var executions = 5;

 var execFunctions = [];

 for (var i = 0; i < executions; ++i) {
    addExecFunction(i);
 }

 var completedExecutions = 0;
 execFunctions.forEach(function(execFunction) {
    execFunction(function(err, val) {
       if (++completedExecutions == executions) {
          console.log('all complete!');
       }
    });
 });

 function addExecFunction(i) {
    execFunctions.push(function(callback) {
       console.log(i + ' start');
       var pwd = execSync.exec('cd && pwd').stdout.replace('\n', '');
       //var pwd = '~';
       var command = 'ls -l ' + pwd;
       //console.log(command);
       exec(command, function onProcessTermination(err, stdout, stderr) {
          console.log(i + ' complete');
          callback(null, i);
       });
    });
 }

output:

$ node testExec.js
0 start
1 start
2 start
3 start
4 start
3 complete
4 complete

When commenting out var pwd = execSync.exec(...);, and uncommenting var pwd = '~'; the script works fine.

PS: I'm running this on a linux box.

error while 'npm install execSync'

Could you please tell me why and how to solve it, tks!
here are the message:

npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the execSync package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild

Small problem executing a ruby script with execSync.

I have a ruby server that I execute from command line like this:

ruby script/rails server webrick -e production

When I try executing that command like in the following example, the ruby server quits:

var execSync = require('execSync');
var result = execSync.stdout('ruby script/rails server webrick -e production');
console.log(result);

However, if I use Nodejs's built-in child_process.exec method, then the ruby server runs just fine without stopping, like this:

var util = require('util');
var exec = require('child_process').exec;

exec("ruby script/rails server webrick -e production", function(error, stdout, stderr) {
        console.log(stdout);
        console.log('done.');
});

Any idea why it doesn't work with execSync but works fine with child_process.exec?

Install error (not found node_modules/execSync/install.js)

ubuntu 14.04
node v0.10.33
npm 2.1.10

Error: Cannot find module '/root/repo/node_modules/execSync/install.js'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:906:3
npm ERR! Linux 3.13.0-37-generic
npm ERR! argv "node" "/usr/bin/npm" "install"
npm ERR! node v0.10.33
npm ERR! npm v2.1.10
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: node install.js
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the [email protected] install script 'node install.js'.
npm ERR! This is most likely a problem with the execSync package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js
npm ERR! You can get their info via:
npm ERR! npm owner ls execSync
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /root/repo/npm-debug.log

Dynamic Symbol Retrieval Error: "popen": The handle is invalid.

var execSync = require('execSync');

Error: Dynamic Symbol Retrieval Error: "popen": The handle is invalid.
at DynamicLibrary.get (execSync\node_modules\ffi\lib\dynamic_library.js:112:11)
at execSync\node_modules\ffi\lib\library.js:50:19
at Array.forEach (native)
at Object.Library (execSync\node_modules\ffi\lib\library.js:47:28)
at Object. (execSync\index.js:8:16)
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:362:17)

Troubles with Node 0.12

Having this in both travis and locally.

$ node --version
v0.12.0
$ npm --version
2.5.1
$ nvm --version
0.23.3

module.js:338
    throw err;
          ^
Error: Cannot find module './build/Release/shell'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/home/travis/build/h5bp/html5please/node_modules/execSync/index.js:30:11)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)

node-gyp rebuild step hangs

Hi, I've been trying to install this lib for the past two days and it hangs forever after reaching the node-gyp rebuild step.

➜ assetline $ npm install execSync
npm WARN package.json [email protected] No repository field.
npm http GET https://registry.npmjs.org/execSync
npm http 304 https://registry.npmjs.org/execSync
npm http GET https://registry.npmjs.org/temp
npm http 304 https://registry.npmjs.org/temp

> [email protected] install /Users/Lukas/projects/codelogic/assetline/node_modules/execSync
> node-gyp rebuild

issue installing

from the doc: npm install execSync

To that I say "Hah!" Why do I say 'hah?' Because it doesn't work on the three computers I've tried it on.

C:\Users\foo\Desktop\bar>npm install execSync
npm http GET https://registry.npmjs.org/execSync
npm http 304 https://registry.npmjs.org/execSync
npm http GET https://registry.npmjs.org/ffi
npm http 304 https://registry.npmjs.org/ffi
npm http GET https://registry.npmjs.org/ffi/-/ffi-1.2.4.tgz
npm http 200 https://registry.npmjs.org/ffi/-/ffi-1.2.4.tgz
npm http GET https://registry.npmjs.org/bindings
npm http GET https://registry.npmjs.org/debug
npm http GET https://registry.npmjs.org/ref-struct
npm http GET https://registry.npmjs.org/ref
npm http 304 https://registry.npmjs.org/ref-struct
npm http 304 https://registry.npmjs.org/bindings
npm http 304 https://registry.npmjs.org/debug
npm http 304 https://registry.npmjs.org/ref

[email protected] install C:\Users\foo\node_modules\execSync\node_modules\ffi\node_modules\ref
node-gyp rebuild

C:\Users\foo\node_modules\execSync\node_modules\ffi\node_modules\ref>node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
gyp ERR! configure error
gyp ERR! stack Error: spawn ENOENT
gyp ERR! stack at errnoException (child_process.js:945:11)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:736:34)
gyp ERR! System Windows_NT 6.2.9200
gyp ERR! command "node" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\foo\node_modules\execSync\node_modules\ffi\node_modules\ref
gyp ERR! node -v v0.10.0
gyp ERR! node-gyp -v v0.8.5
gyp ERR! not ok
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! cmd "/c" "node-gyp rebuild" failed with 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the ref package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls ref
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "execSync"
npm ERR! cwd C:\Users\foo\Desktop\bar
npm ERR! node -v v0.10.0
npm ERR! npm -v 1.2.14
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\Users\foo\Desktop\bar\npm-debug.log
npm ERR! not ok code 0

C:\Users\foo\Desktop\bar>

If there's some clue to the problem (a problem I can fix) then I can't see it.