Created
June 10, 2014 23:51
-
-
Save wfwalker/d932431e5caa88f5fc1a to your computer and use it in GitHub Desktop.
tried to deploy updated thecount to stackato, hit npm problems
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
staging: npm ERR! Error: ENOENT, lstat '/staging/staged/app/node_modules/express/node_modules/accepts/node_modules/negotiator/LICENSE' | |
staging: npm ERR! { [Error: ENOENT, lstat '/staging/staged/app/node_modules/express/node_modules/accepts/node_modules/negotiator/LICENSE'] | |
staging: npm ERR! errno: 34, | |
staging: npm ERR! code: 'ENOENT', | |
staging: npm ERR! path: '/staging/staged/app/node_modules/express/node_modules/accepts/node_modules/negotiator/LICENSE', | |
staging: npm ERR! fstream_type: 'File', | |
staging: npm ERR! fstream_path: '/staging/staged/app/node_modules/express/node_modules/accepts/node_modules/negotiator/LICENSE', | |
staging: npm ERR! fstream_class: 'FileWriter', | |
staging: npm ERR! fstream_stack: [ 'Object.oncomplete (/usr/lib/node_modules/npm/node_modules/fstream/lib/writer.js:284:26)' ] } | |
staging: npm ERR! You may report this log at: | |
staging: npm ERR! <http://github.com/isaacs/npm/issues> | |
staging: npm ERR! or email it to: | |
staging: npm ERR! <npm-@googlegroups.com> | |
staging: | |
staging: npm ERR! System Linux 3.2.0-36-virtual | |
staging: npm ERR! command "node" "/usr/bin/npm" "install" | |
staging: npm ERR! cwd /staging/staged/app | |
staging: npm ERR! node -v v0.6.20 | |
staging: npm ERR! npm -v 1.1.37 | |
staging: npm ERR! path /staging/staged/app/node_modules/express/node_modules/accepts/node_modules/negotiator/LICENSE | |
staging: npm ERR! fstream_path /staging/staged/app/node_modules/express/node_modules/accepts/node_modules/negotiator/LICENSE | |
staging: npm ERR! fstream_type File | |
staging: npm ERR! fstream_class FileWriter | |
staging: npm ERR! code ENOENT | |
staging: npm ERR! message ENOENT, lstat '/staging/staged/app/node_modules/express/node_modules/accepts/node_modules/negotiator/LICENSE' | |
staging: npm ERR! errno 34 | |
staging: npm ERR! fstream_stack Object.oncomplete (/usr/lib/node_modules/npm/node_modules/fstream/lib/writer.js:284:26) | |
staging: npm ERR! 34 errno | |
staging: npm ERR! Error: ENOENT, open '/staging/staged/app/node_modules/express/node_modules/accepts/node_modules/mime/package.json' | |
staging: npm ERR! { [Error: ENOENT, open '/staging/staged/app/node_modules/express/node_modules/accepts/node_modules/mime/package.json'] | |
staging: npm ERR! errno: 34, | |
staging: npm ERR! code: 'ENOENT', | |
staging: npm ERR! path: '/staging/staged/app/node_modules/express/node_modules/accepts/node_modules/mime/package.json' } | |
staging: npm ERR! You may report this log at: | |
staging: npm ERR! <http://github.com/isaacs/npm/issues> | |
staging: npm ERR! or email it to: | |
staging: npm ERR! <npm-@googlegroups.com> | |
staging: | |
staging: npm ERR! System Linux 3.2.0-36-virtual | |
staging: npm ERR! command "node" "/usr/bin/npm" "install" | |
staging: npm ERR! cwd /staging/staged/app | |
staging: npm ERR! node -v v0.6.20 | |
staging: npm ERR! npm -v 1.1.37 | |
staging: npm ERR! path /staging/staged/app/node_modules/express/node_modules/accepts/node_modules/mime/package.json | |
staging: npm ERR! code ENOENT | |
staging: npm ERR! message ENOENT, open '/staging/staged/app/node_modules/express/node_modules/accepts/node_modules/mime/package.json' | |
staging: npm ERR! errno 34 | |
staging: npm ERR! 34 errno | |
staging: npm WARN engine form-data@0.1.3: wanted: {"node":">= 0.8"} (current: {"node":"0.6.20","npm":"1.1.37"}) | |
staging: npm WARN engine http-signature@0.10.0: wanted: {"node":">=0.8"} (current: {"node":"0.6.20","npm":"1.1.37"}) | |
staging: npm WARN engine hawk@1.0.0: wanted: {"node":">=0.8.0"} (current: {"node":"0.6.20","npm":"1.1.37"}) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment