npm link fails (express and qs) #2524

Closed
faruk opened this Issue Jun 13, 2012 · 1 comment

Projects

None yet

2 participants

@faruk
faruk commented Jun 13, 2012

Hello, I got the following output when trying to "npm link" my coffee
application.

I use latest Debian Testing.
Linux goku 2.6.32-5-amd64 #1 SMP Thu Mar 22 17:26:33 UTC 2012 x86_64 GNU/Linux

here the ouput

faruk@goku:~/work/ichron/coffeechron$ npm link
npm WARN express-form@0.6.2 package.json: bugs['web'] should probably
be bugs['url']
npm http GET https://registry.npmjs.org/express
npm http 304 https://registry.npmjs.org/express
npm http GET https://registry.npmjs.org/connect
npm http GET https://registry.npmjs.org/qs
npm http GET https://registry.npmjs.org/mime/1.2.4
npm http GET https://registry.npmjs.org/mkdirp/0.3.0
npm http 304 https://registry.npmjs.org/qs
npm http 304 https://registry.npmjs.org/mime/1.2.4
npm http 304 https://registry.npmjs.org/mkdirp/0.3.0
npm http 200 https://registry.npmjs.org/connect
npm ERR! error installing qs@0.4.2
npm ERR! error installing express@2.5.9

npm ERR! Error: ENOENT, no such file or directory
'/home/faruk/work/ichron/coffeechron/node_modules/express/node_modules/qs/package.json'
npm ERR! You may report this log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! npm-@googlegroups.com
npm ERR!
npm ERR! System Linux 2.6.32-5-amd64
npm ERR! command "node" "/opt/node/bin/npm" "link"
npm ERR! cwd /home/faruk/work/ichron/coffeechron
npm ERR! node -v v0.6.9
npm ERR! npm -v 1.1.0-3
npm ERR! path /home/faruk/work/ichron/coffeechron/node_modules/express/node_modules/qs/package.json
npm ERR! code ENOENT
npm ERR! message ENOENT, no such file or directory
'/home/faruk/work/ichron/coffeechron/node_modules/express/node_modules/qs/package.json'
npm ERR! errno {}
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/faruk/work/ichron/coffeechron/npm-debug.log
npm not ok

faruk@goku:~/work/ichron/coffeechron/node_modules/express/node_modules$ ls
connect mime mkdirp

what could i do about this? the log is empty

Thanks in advance,

faruk

@isaacs
Member
isaacs commented Jun 18, 2012
  1. Update to the latest npm. (You're using a beta from many months ago.)
  2. npm cache clean
  3. Win.
@isaacs isaacs closed this Jun 18, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment