I'm very new to Node.js and npm -- basically have just used to install modules as described, and up until a few days ago it always just worked. However now pretty much when I install anything, I get a LOT of errors in the output. I may be dumb, but the errors also seem to contain no information about what the actual error is.
Any help is appreciated. I'd be happy to just blow away Node.js entirely and reinstall, but haven't been able to do that either.
The output says to send the entire log here, but I don't see how to do that. It's too long for this input form. Here's the tail end. All the errors look about the same as this:
3827 silly gunzTarPerm extractEntry lib/fileset.js
3828 silly gunzTarPerm extractEntry tests/helper.js
3829 info preinstall firstname.lastname@example.org
3830 silly gunzTarPerm extractEntry example/sync.js
3831 silly gunzTarPerm extractEntry lib/async.js
3832 error Error: ENOENT, lstat '/Library/WebServer/Documents/angular-app/client/node_modules/grunt-karma/node_modules/karma/node_modules/istanbul/node_modules/escodegen/README.md'
3833 error If you need help, you may report this *entire* log,
3833 error including the npm and node versions, at:
3833 error <http://github.com/npm/npm/issues>
3834 error System Darwin 13.0.0
3835 error command "node" "/usr/local/bin/npm" "install"
3836 error cwd /Library/WebServer/Documents/angular-app/client
3837 error node -v v0.10.25
3838 error npm -v 1.4.4
3839 error path /Library/WebServer/Documents/angular-app/client/node_modules/grunt-karma/node_modules/karma/node_modules/istanbul/node_modules/escodegen/README.md
3840 error fstream_path /Library/WebServer/Documents/angular-app/client/node_modules/grunt-karma/node_modules/karma/node_modules/istanbul/node_modules/escodegen/README.md
3841 error fstream_type File
3842 error fstream_class FileWriter
3843 error code ENOENT
3844 error errno 34
3845 error fstream_stack /usr/local/lib/node_modules/npm/node_modules/fstream/lib/writer.js:284:26
3845 error fstream_stack Object.oncomplete (fs.js:107:15)
3846 verbose exit [ 34, true ]
It looks like this can be an effect of some corrupted stuff in the cache. Does it happen every time, or was it a sporadic issue? Try running npm cache clean and see if that makes things good.
npm cache clean
I did see a few other reports of publishing returning 503 and other errors. We're looking into this now.
I'm seeing much the same thing, but I'm pushing my node projects to dokku. My entire error log is here: http://pastebin.com/EJjbSdzW
Closing as abandoned. If you install the latest stable version of npm, this problem will probably go away, because we've put a lot of effort into rooting out race conditions in the npm installer over the past few months.