New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm install -g gives ENOENT #1
Comments
Same here nick@devbox:~/myproject$ npm install --save -g solgraph
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
/home/nick/.npm-global/lib
└── (empty)
npm WARN optional Skipping failed optional dependency /solgraph/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.12
npm ERR! Linux 4.4.0-28-generic
npm ERR! argv "/usr/local/bin/node" "/usr/bin/npm" "install" "--save" "-g" "solgraph"
npm ERR! node v6.2.1
npm ERR! npm v3.9.5
npm ERR! path /home/nick/.npm-global/lib/node_modules/solgraph/dist/solgraph.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/home/nick/.npm-global/lib/node_modules/solgraph/dist/solgraph.js'
npm ERR! enoent ENOENT: no such file or directory, chmod '/home/nick/.npm-global/lib/node_modules/solgraph/dist/solgraph.js'
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! /home/nick/myproject/npm-debug.log
npm ERR! code 1 |
I think it probably has to do with the node life cycle. It is linking the binary before it does the postinstall step. I'm going to investigate to see if that's the case. |
https://stackoverflow.com/questions/17990647/npm-install-errors-with-error-enoent-chmod
|
@jorisbontje Trying that now. |
Thanks @jorisbontje! I would not have found that on my own. |
npm ERR! Please include the following file with any support request:
npm ERR! /Users/mids/npm-debug.log
npm ERR! code 1
The text was updated successfully, but these errors were encountered: