install fails in OSX 10.10.2 / Node 0.12.4

[jcollum]

$ sw_vers -productVersion
10.10.2
$ node --version
v0.12.4
$ which node
/Users/collumj/.nvm/versions/node/v0.12.4/bin/node

The error lines from the output are:

11491 error Darwin 14.1.0
11492 error argv "/Users/collumj/.nvm/versions/node/v0.12.4/bin/node" "/Users/collumj/.nvm/versions/node/v0.12.4/bin/npm" "--no-bin-links" "install" "-g" "node-inspector"
11493 error node v0.12.4
11494 error npm  v2.10.1
11495 error file sh
11496 error code ELIFECYCLE
11497 error errno ENOENT
11498 error syscall spawn
11499 error v8-debug@0.4.6 install: `node-pre-gyp install --fallback-to-build`
11499 error spawn ENOENT
11500 error Failed at the v8-debug@0.4.6 install script 'node-pre-gyp install --fallback-to-build'.
11500 error This is most likely a problem with the v8-debug package,
11500 error not with npm itself.
11500 error Tell the author that this fails on your system:
11500 error     node-pre-gyp install --fallback-to-build

I don't appear to have node-pre-gyp installed but shouldn't it be installing that as a dependency? Maybe nvm is the culprit?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[jcollum]

This may be related node-inspector/v8-debug#7

[xErik]

Same here.

Workaround: sudo npm install -g node-inspector --unsafe-perm

[jlazerus]

Thanks @xErik this workaround fixed my problem also.

[jcollum]

I went back to v0.10.38 (via nvm) and tried to install node-inspector with -g and it installed with no problems.

[3y3]

@jcollum , is sudo npm install -g node-inspector --unsafe-perm helpful for you?

[jcollum]

I generally avoid installing things with sudo (in node). Unsafe-perm also sounds like something to be avoided. It's fine, I nvm'd my node to 0.12.2 and it installed with no issues.

[3y3]

Can I close this as solved?

[jcollum]

It's not solved. The workarounds involve downgrading to 0.12.2 or installing with sudo, which is generally advised against.

[3y3]

I'm not very friendly with OSX can anyone explain me, why we need to use sudo and --unsafe-perm here? And why not all users on OSX should use this workaround, what is special here?

[jpbufe3]

I am also seeing a very similar problem:

       npm ERR! Linux 3.13.0-39-generic
       npm ERR! argv "/tmp/staged/app/vendor/node/bin/node" "/tmp/staged/app/vendor/node/bin/npm" "rebuild"
       npm ERR! node v0.12.2
       npm ERR! npm  v2.7.4
       npm ERR! code ELIFECYCLE
       npm ERR! v8-debug@0.4.6 install: `node-pre-gyp install --fallback-to-build`
       npm ERR! Exit status 127
       npm ERR! 
       npm ERR! Failed at the v8-debug@0.4.6 install script 'node-pre-gyp install --fallback-to-build'.
       npm ERR! This is most likely a problem with the v8-debug package,
       npm ERR! not with npm itself.
       npm ERR! Tell the author that this fails on your system:
       npm ERR!     node-pre-gyp install --fallback-to-build

[duro]

I am getting this in Debian linux as well inside a Docker container, which runs npm as root in this case.

[duro]

The work around does work for me, but it also seems like not something that should be accepted as done

[chuckweinberger]

I'm seeing a similar problem with v8-profiler. Any advice?

[nw-html-client (new-file-structure)]$ sudo npm install -g node-inspector --unsafe-perm
Password:

v8-profiler@5.3.0 preinstall /Users/charlesweinberger/.node_modules_global/lib/node_modules/node-inspector/node_modules/v8-profiler

v8-debug@0.5.2 preinstall /Users/charlesweinberger/.node_modules_global/lib/node_modules/node-inspector/node_modules/v8-debug

\

utf-8-validate@1.2.1 install /Users/charlesweinberger/.node_modules_global/lib/node_modules/node-inspector/node_modules/ws/node_modules/utf-8-validate
node-gyp rebuild

CXX(target) Release/obj.target/validation/src/validation.o
SOLINK_MODULE(target) Release/validation.node
SOLINK_MODULE(target) Release/validation.node: Finished
npm WARN engine xmlbuilder@2.2.1: wanted: {"node":"0.8.x || 0.10.x"} (current: {"node":"0.12.7","npm":"2.10.1"})

bufferutil@1.2.1 install /Users/charlesweinberger/.node_modules_global/lib/node_modules/node-inspector/node_modules/ws/node_modules/bufferutil
node-gyp rebuild

CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
SOLINK_MODULE(target) Release/bufferutil.node
SOLINK_MODULE(target) Release/bufferutil.node: Finished

v8-profiler@5.3.0 install /Users/charlesweinberger/.node_modules_global/lib/node_modules/node-inspector/node_modules/v8-profiler
node-pre-gyp install --fallback-to-build

sh: node-pre-gyp: command not found

v8-debug@0.5.2 install /Users/charlesweinberger/.node_modules_global/lib/node_modules/node-inspector/node_modules/v8-debug
node-pre-gyp install --fallback-to-build

sh: node-pre-gyp: command not found
npm ERR! Darwin 14.3.0
npm ERR! argv "node" "/Users/charlesweinberger/.node_modules_global/bin/npm" "install" "-g" "node-inspector" "--unsafe-perm"
npm ERR! node v0.12.7
npm ERR! npm v2.10.1
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR! v8-profiler@5.3.0 install: node-pre-gyp install --fallback-to-build
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the v8-profiler@5.3.0 install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! This is most likely a problem with the v8-profiler package,

[CoreSoft2]

Same here , any work-around? NPM supposes to be next generation package management software, not to go through all the problems we have with YUM, apt-get etc. etc., back to where we were!

[hugowschneider]

Same here! OSX 10.11.1 NPM v3.3.6 Node v5.0.0

[granteagon]

Same issue here.