npm install errors with Error: ENOENT, chmod

npm err! code enoent
npm err! code enoent npm err! syscall open
npm err! code enoent npm err! syscall spawn git
npm err! enoent this is related to npm not being able to find a file.
install npm
npm err! code enoent angular
npm err! errno -4058
npm error -4058

I am trying to globally install an npm module I just published. Every time I try to install, either from npm or the folder, I get this error.

npm ERR! Error: ENOENT, chmod '/usr/local/lib/node_modules/takeapeek/lib/cmd.js'
npm ERR! If you need help, you may report this log at:
npm ERR!     <>
npm ERR! or email it to:
npm ERR!     <>

npm ERR! System Linux 3.8.0-19-generic
npm ERR! command "node" "/usr/local/bin/npm" "install" "-g" "takeapeek"
npm ERR! cwd /home/giodamlio
npm ERR! node -v v0.10.6
npm ERR! npm -v 1.3.6
npm ERR! path /usr/local/lib/node_modules/takeapeek/lib/cmd.js
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/giodamlio/npm-debug.log
npm ERR! not ok code 0

I am using sudo and I have triple checked everything in the package everything should work. I did some searching around, and saw a couple of similer cases none of which have been resolved. Here is what I tried.

  • Upgrade npm (sudo npm install -g npm)
  • Clear the global npm cache (sudo npm cache clear)
  • Clear the user npm cache (npm cache clear)

I noticed that the error had to do with the file I am linking to the path, specifically when npm tried to do a chmod. That shouldn't be a problem, my lib/cli.js has normal permissions, and npm has superuser permissions during this install.

After digging through the npm docs I found an option that would stop npm from making the bin links(--no-bin-links), when I tried the install with it, it worked fine.

So what's the deal? Is this some weird fringe case bug that has no solution yet?

Edit: For reference, here is the module I uploaded

Ok it looks like NPM is using your .gitignore as a base for the .npmignore file, and thus ignores /lib. If you add a blank .npmignore file into the root of your application, everything should work.

[edit] - more info on this behaviour here:

Common errors, Not sure where the issue is but I am unable to install sqlite3 in an .com/​questions/17990647/npm-install-errors-with-error-enoent-chmod  npm install errors with Error: ENOENT, chmod. I am trying to globally install an npm module I just published. Every time I try to install, either from npm or the

I ran into a similar problem,

npm cache clean

solved it.

ENOENT: no such file or directory, chmod · Issue #620 · mapbox , Error: ENOENT, chmod '/usr/lib/node_modules/crest/bin/server' npm ERR! Created blank .npmignore to avoid install errors #2. Open. Dismiss Join GitHub today. GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

This problem somehow arose for me on Mac when I was trying to run npm install -g bower. It was giving me a number of errors for not being able to find things like graceful-fs. I'm not sure how I installed npm originally, but it looks like perhaps it came down with node using homebrew. I first ran

brew uninstall node

This removed both node and npm from my path. From there I just reinstalled it

brew install node

When it completed I had node and npm on my path and I was able to run

rm -rf ~/.npm
npm install -g bower

This then installed bower successfully.

Updating the brew formulas and upgrading the installs didn't seem to work for me, I'm not sure why. The removal of the .npm folder was something that had worked for other people, and I had tried it without success. I did it this time just in case. Note also that neither of the following solved the problem for me, although it did for others:

npm cache clean
sudo npm cache clean

npm install exits with Error: ENOENT, chmod · Issue #1 · Cordazar , After running npm install --save-dev sqlite3, each subsequent time I try to run npm install I get an error relating to "ENOENT: no such file or If I keep the package-lock.json in place and install again, then the install fails. Hi, we encounter this issue. does anybody know what is the root cause and how to fix? it works fine on local, but not work on cloud. Thanks, Bruce Xie 0 info it worked if it ends with ok 1 verbose

I was getting this error on npm install and adding .npmignore did not solve it.

Error: ENOENT, stat 'C:\Users\My-UserName\AppData\Roaming\npm'

I tried going to the mentioned folder and it did not exist. The error was fixed when I created npm folder in Roaming folder.

This is on Windows 8.1

"ENOENT: no such file or directory, rename " when running npm , Every time I try to install, either from npm or the folder, I get this error. npm ERR! Error: ENOENT, chmod '/usr/local/lib/node_modules/takeapeek/lib/cmd.js' npm  Tried npm install websockify Using Node.js v0.10.17 download, OSX 10.8.3, get the following error: (I checked, websockify.js file doesn't get installed, I've tried running with sudo as well, dir permissions are drwxr-xr-x.

I had the same problem, and just found a handling not mentioned here. Though I'd contribute to the community:

npm install -g myapp was not copying the bin directory. I found this to be because I did not include it in the files in my package.json

"files": [
  "bin" // this was missing

npm install errors with Error: ENOENT, chmod - node.js - html, npm ERR! Error: ENOENT, chmod '/usr/local/lib/node_modules/takeapeek/lib/​cmd.js' npm ERR! If you need help, you may report this log at:  Many ENOENT / ENOTEMPTY errors in output. npm is written to use resources efficiently on install, and part of this is that it tries to do as many things concurrently as is practical. Sometimes this results in race conditions and other synchronization issues. As of npm 2.0.0, a very large number of these issues were addressed.

npm install errors with Error: ENOENT, chmod, node.js - npm install errors with Error: ENOENT, chmod In my case (multiple code ENOENT errno 34) problem was with ~/.npm/ directory  dans mon cas (code multiple ENOENT errno 34) problème était avec ~/.npm/ l'accès à l'annuaire. À l'intérieur il y avait quelques sous-répertoires ayant les droits root:root, qui causaient des problèmes pendant que j'exécutais des commandes en tant qu'utilisateur normal (sans sudo).

npm enoent error - Search, If you are experiencing issues with npm install, you will need to use the Error: ENOENT, stat 'C:\Users\ \AppData\Roaming\npm' on Windows 7 If you see errors like, ENOENT lstat, ENOENT chmod, ENOTEMPTY unlink,  errors after npm install. GitHub Gist: instantly share code, notes, and snippets.

npm - Common Errors, I have Ubuntu 12.10 running as a VMware guest on my Windows 8 host. I have shared a folder on my Windows 8 Host and it is mounted in the Ubuntu guest on startup using this entry in fstab: //myhos

  • is your package using node-gyp? I think that no-bin-links call is related if so.
  • Nope, no native code in the module. Here is the module source for reference.
  • The --no-bin-links just stops npm from symlinking files in the package.json's bin hash to the path on global install.
  • Argh, I've definitely run into this before but I can't remember why... will let you know if it pops into my head.
  • @jcollum Thanks, its really quite frustrating, I have checked everything a billion times, but I still can't help feeling I've missed something stupid simple. That or maybe it is some weird bug.
  • Darn, that must be it. That seems like a bit of a confusing way of doing things. Not at a computer now, but I will try it in a few hours.
  • Yea it took me a while to figure it out. Some guys more experienced than I hinted this on the reddit thread.
  • I tested this using your repo and installing locally using npm install ../takeapeek and adding the blank .npmignore file works.
  • 3 hours of frustration came down to one line in my .gitignore that was freaking out the npm install -g. Insane.
  • 'type NUL > .npmignore' for windows
  • I tried npm cache verify and it worked. thanks for hint.
  • npm cache clean --force worked for me
  • Got the same issue and this answer was the only good fix for me. The reason was I got the files key in my package.json with some entries like index.js and LICENSE, but not the bin folder. So it works if there is no files key at all, or if there is a files key AND the bin folder into.
  • Thanks, this helped me get unstuck. Once you pointed out that the bin directory wasn't included in files I thought "oh! of course!". Then I went back to the docs to see if I missed it and it's not mentioned (at least not in the npm blog post I was reading through). At least I'm not crazy :P. Thanks for the help!