-
Notifications
You must be signed in to change notification settings - Fork 50
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
ENOENT during npm install #16
Comments
Same here. Vagrant machine is affected. |
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 |
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 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. |
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: |
Most of my debug log is here: https://gist.github.com/kevingelion/7343d98fa5734719fed06085fe8ddd69
The text was updated successfully, but these errors were encountered: