HomeBlogsgstevens's blognpm update -g <foo> causes ENOENT on lstat

npm update -g <foo> causes ENOENT on lstat

If you have tried to recently update your global node_modules, you may have had a series of errors saying ENOENT. For example:

npm ERR! System Darwin 13.1.0
npm ERR! command "node" "/usr/local/bin/npm" "update" "-g" "yo"
npm ERR! cwd /Users/gstevens
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.4
npm ERR! path /usr/local/lib/node_modules/yo/node_modules/yeoman-generator/node_modules/isbinaryfile/README.md
npm ERR! fstream_path /usr/local/lib/node_modules/yo/node_modules/yeoman-generator/node_modules/isbinaryfile/README.md
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/local/lib/node_modules/npm/node_modules/fstream/lib/writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, lstat '/usr/local/lib/node_modules/yo/node_modules/yeoman-generator/node_modules/iconv-lite/README.md'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR! http://github.com/npm/npm/issues

This problem has been identified on the npm issue list at github. For most people, the fix is to clean the npm cache:

npm cache clean


Post new comment

This question is for testing whether you are a human visitor and to prevent automated spam submissions.
Enter the characters shown in the image.