ENOENT during npm install

[weedgrease]

npm ERR! Linux 3.13.0-96-generic
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.10.25
npm ERR! npm  v3.10.8
npm ERR! path /vagrant/dashboard/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/sshpk/bin/sshpk-conv
npm ERR! code ENOENT
npm ERR! errno 34

npm ERR! enoent ENOENT, chmod '/vagrant/dashboard/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/sshpk/bin/sshpk-conv'
npm ERR! enoent ENOENT, chmod '/vagrant/dashboard/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/sshpk/bin/sshpk-conv'
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

Most of my debug log is here: https://gist.github.com/kevingelion/7343d98fa5734719fed06085fe8ddd69

[tkgalk]

Same here. Vagrant machine is affected.

[austinried]

Was there ever a workaround or solution to this discovered? I am trying to upgrade an existing project to node 6 and I'm unable to run npm install due to another module's dependency on this package and the above error.

[arekinath]

The published sshpk packages definitely all contain the file being complained about in the log above. In the debug log linked, you can clearly see the sshpk-conv file being extracted by npm earlier in the process.

I also can't reproduce this on any node or npm version I have access to (or any running on prod machines at Joyent). So, in short, I'm having trouble understanding how this can be an issue with sshpk. If someone with access to a machine experiencing the problem can debug it further and suggest a fix, I'm happy to take it, but I don't have any suggestions, sorry.

[RiverSongFox]

I had a similar issue with npm 4.1.2, and it disappeared after updating to latest 4.6.1. There is also a workaround for the issue: npm install --no-bin-links; in this case, npm won't attempt to chmod these files.