Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


install error #5774

mcdlt opened this Issue · 5 comments

4 participants

npm ERR! Error: ENOENT, open '/private/var/root/package.json'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <>

npm ERR! System Darwin 13.3.0
npm ERR! command "node" "/usr/local/bin/npm" "test"
npm ERR! cwd /private/var/root
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! path /private/var/root/package.json
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /private/var/root/npm-debug.log
npm ERR! not ok code 0

Does /private/var/root/package.json exist? If not, npm won't know what you want it to do when you run npm test.


It doesn't exist. I guess my issue is in the nstaller. Still not sure how to fix it though. This is the install error log:

0 info it worked if it ends with ok
1 verbose cli [ 'node', '/usr/local/bin/npm', 'start' ]
2 info using npm@1.4.14
3 info using node@v0.10.29
4 error Error: ENOENT, open '/private/var/root/package.json'
5 error If you need help, you may report this entire log,
5 error including the npm and node versions, at:
5 error
6 error System Darwin 13.3.0
7 error command "node" "/usr/local/bin/npm" "start"
8 error cwd /private/var/root
9 error node -v v0.10.29
10 error npm -v 1.4.14
11 error path /private/var/root/package.json
12 error code ENOENT
13 error errno 34
14 verbose exit [ 34, true ]


MacDLT:angular-phonecat root# npm install

npm WARN package.json karma-chrome-launcher@0.1.4 No README data
npm WARN cannot run in wd angular-phonecat@0.0.0 bower install (wd=/Users/mcdlt/Documents/www/angular-phonecat)


Looks like you're trying to run npm start in a directory (/private/var/root) that doesn't have a package.json. npm won't know what you want to "start" unless there's a package.json in your current working directory.

@iarna iarna added the support label

Closing as resolved – @KenanY's explanation of what's going on is correct.

@othiym23 othiym23 closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.