Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

error Error: ENOENT, lstat '/usr/local/lib/node_modules/jshint/node_modules/cli/node_modules/glob/node_modules/mkdirp/node_modules/tap/node_modules/runforcover/node_modules/bunker/node_modules/burrito/index.js' #2849

JLewis604 opened this Issue Oct 2, 2012 · 1 comment


None yet
2 participants

error Error: ENOENT, lstat '/usr/local/lib/node_modules/jshint/node_modules/cli/node_modules/glob/node_modules/mkdirp/node_modules/tap/node_modules/runforcover/node_modules/bunker/node_modules/burrito/index.js'
22204 error If you need help, you may report this log at:
22204 error http://github.com/isaacs/npm/issues
22204 error or email it to:
22204 error npm-@googlegroups.com
22205 error System Linux 3.2.0-31-generic
22206 error command "/usr/local/bin/node" "/usr/local/bin/npm" "install" "recess" "connect" "uglify-js" "jshint" "-g"
22207 error cwd /usr/local/lib/node_modules
22208 error node -v v0.8.11
22209 error npm -v 1.1.62
22210 error path /usr/local/lib/node_modules/jshint/node_modules/cli/node_modules/glob/node_modules/mkdirp/node_modules/tap/node_modules/runforcover/node_modules/bunker/node_modules/burrito/index.js
22211 error fstream_path /usr/local/lib/node_modules/jshint/node_modules/cli/node_modules/glob/node_modules/mkdirp/node_modules/tap/node_modules/runforcover/node_modules/bunker/node_modules/burrito/index.js
22212 error fstream_type File
22213 error fstream_class FileWriter
22214 error code ENOENT
22215 error errno 34
22216 error fstream_stack Writer._finish.er.fstream_finish_call (/usr/local/lib/node_modules/npm/node_modules/fstream/lib/writer.js:284:26)
22216 error fstream_stack Object.oncomplete (fs.js:297:15)
22217 verbose exit [ 34, true ]

Attempting to run:

$ npm install recess connect uglify-js jshint -g


Ubuntu 12.04 LTS
npm version 1.1.62
node version 0.8.11

... Any help you can provide would be greatly appreciated :D


isaacs commented Oct 3, 2012

Can you share the rest of the error log?

My guess is that there are a bunch of existing entries in the npm cache, resulting in 304 responses from the http requests, and that the problem will go away if you do npm cache clean.

@isaacs isaacs closed this Oct 3, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment