Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Mac npm erroring with ENOENT

I'm a recent convert to Mac from Windows, and currently just trying to get my tools setup.

I first installed node using homebrew, which was giving me errors (same as what I still have). I later removed node using homebrew and installed using the pkg from the node website.

I can access node in the command line and npm. The problem is when I try to install modules on the project locally I get something like:

npm install grunt-contrib

Error extracting archive { [Error: ENOENT, open '/Users/davidmckeown/dev/adt-com/node_modules/grunt-contrib/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/tmp/phantomjs-1.7.0-macosx.zip']
  errno: 34,
  code: 'ENOENT',
  path: '/Users/davidmckeown/dev/adt-com/node_modules/grunt-contrib/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/tmp/phantomjs-1.7.0-macosx.zip' }

Another message just above that contains:

npm ERR! [email protected] install: `node install.js`
npm ERR! `sh "-c" "node install.js"` failed with 8
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the phantomjs 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 phantomjs
npm ERR! There is likely additional logging output above.

npm ERR! System Darwin 12.2.1
npm ERR! command "node" "/usr/local/bin/npm" "install" "grunt-contrib"
npm ERR! cwd /Users/davidmckeown/dev/adt-com
npm ERR! node -v v0.10.0
npm ERR! npm -v 1.2.14
npm ERR! code ELIFECYCLE

Any help figuring out what is causing problems here would be fantastic. This happens with other modules too, from what I can tell.

like image 320
David Avatar asked Mar 18 '13 17:03

David


People also ask

Why npm install showing error?

This means that npm fails to install the node-sass module that's added as a dependency to the n-app project. To resolve this error, you need to upgrade the dependency module that causes the error.


1 Answers

npm cache clean

or if installed under su

sudo npm cache clean

like image 119
Roman Rhrn Nesterov Avatar answered Oct 21 '22 14:10

Roman Rhrn Nesterov