Skip to content
This repository was archived by the owner on Feb 26, 2024. It is now read-only.

Npm install error #271

Closed
samx opened this issue May 14, 2015 · 2 comments
Closed

Npm install error #271

samx opened this issue May 14, 2015 · 2 comments

Comments

@samx
Copy link

samx commented May 14, 2015

I've been able to get this to work in the past. Recently tried to run npm install on an unedited angular-seed repo. But get errors and "node start" fails to initalize the server

[email protected] install /Users/macbookpro/.Trash/angular-seed-master/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
(node-gyp rebuild 2> builderror.log) || (exit 0)

CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
SOLINK_MODULE(target) Release/bufferutil.node
SOLINK_MODULE(target) Release/bufferutil.node: Finished
CXX(target) Release/obj.target/validation/src/validation.o
SOLINK_MODULE(target) Release/validation.node
SOLINK_MODULE(target) Release/validation.node: Finished
npm ERR! Darwin 14.0.0
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.2
npm ERR! npm v2.7.4
npm ERR! path /Users/macbookpro/.Trash/angular-seed-master/node_modules/karma/node_modules/chokidar/package.json
npm ERR! code ENOENT
npm ERR! errno -2

npm ERR! enoent ENOENT, open '/Users/macbookpro/.Trash/angular-seed-master/node_modules/karma/node_modules/chokidar/package.json'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR! /Users/macbookpro/.Trash/angular-seed-master/npm-debug.log

@angajime
Copy link

Same issue here... It looks like there is something wrong with pakage.json but it is passing on jsonlint.com

Edit: My problem was my own NPM global installation. I fixed it cleaning every globally installed NPM package... Hope it helps!

@gkalpak
Copy link
Member

gkalpak commented Jun 19, 2016

As stated in the error message above (and verified by @angajime):

This is most likely not a problem with npm itself

Closing since this isn't related to angular-seed.

@gkalpak gkalpak closed this as completed Jun 19, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants