node.js - nodejs npm unable to install globally from github URL -

i able install locally using git url

how install npm package github directly?

however, once add "-g" flag - fails.

here entire log

guym@guym-ubuntu:~/dev_env/projects_git/cosmo/gs-tmp$ sudo npm -g install git://github.com/visionmedia/express.git npm http https://registry.npmjs.org/connect/2.8.3 npm http https://registry.npmjs.org/commander/1.2.0 npm http https://registry.npmjs.org/range-parser/0.0.4 npm http https://registry.npmjs.org/mkdirp/0.3.5 npm http https://registry.npmjs.org/cookie/0.1.0 npm http https://registry.npmjs.org/buffer-crc32/0.2.1 npm http https://registry.npmjs.org/fresh/0.1.0 npm http https://registry.npmjs.org/methods/0.0.1 npm http https://registry.npmjs.org/cookie-signature/1.0.1 npm http https://registry.npmjs.org/send/0.1.2 npm http https://registry.npmjs.org/debug npm http 304 https://registry.npmjs.org/connect/2.8.3 npm http 304 https://registry.npmjs.org/range-parser/0.0.4 npm warn package.json range-parser@0.0.4 no repository field. npm http 304 https://registry.npmjs.org/cookie/0.1.0 npm http 304 https://registry.npmjs.org/commander/1.2.0 npm http 304 https://registry.npmjs.org/mkdirp/0.3.5 npm http 304 https://registry.npmjs.org/buffer-crc32/0.2.1 npm http 304 https://registry.npmjs.org/fresh/0.1.0 npm warn package.json fresh@0.1.0 no repository field. npm http 304 https://registry.npmjs.org/methods/0.0.1 npm warn package.json methods@0.0.1 no repository field. npm warn package.json methods@0.0.1 no readme data. npm http 304 https://registry.npmjs.org/cookie-signature/1.0.1 npm warn package.json cookie-signature@1.0.1 no repository field. npm http 304 https://registry.npmjs.org/send/0.1.2 npm http 304 https://registry.npmjs.org/debug npm http https://registry.npmjs.org/mime npm http https://registry.npmjs.org/keypress npm http https://registry.npmjs.org/qs/0.6.5 npm http https://registry.npmjs.org/formidable/1.0.14 npm http https://registry.npmjs.org/bytes/0.2.0 npm http https://registry.npmjs.org/uid2/0.0.2 npm http https://registry.npmjs.org/pause/0.0.1 npm http 304 https://registry.npmjs.org/mime npm http 304 https://registry.npmjs.org/keypress npm http 304 https://registry.npmjs.org/qs/0.6.5 npm http 304 https://registry.npmjs.org/bytes/0.2.0 npm warn package.json bytes@0.2.0 no repository field. npm http 304 https://registry.npmjs.org/formidable/1.0.14 npm http 304 https://registry.npmjs.org/uid2/0.0.2 npm http 304 https://registry.npmjs.org/pause/0.0.1 npm warn package.json uid2@0.0.2 no repository field. npm warn package.json uid2@0.0.2 no readme data. npm warn package.json pause@0.0.1 no repository field. /usr/bin/express -> /usr/lib/node_modules/express/bin/express npm warn package.json cli-table@0.2.0 no repository field. npm warn package.json cheerio-select@0.0.3 no repository field. npm warn package.json github-url-from-git@1.1.1 no repository field. npm warn package.json assert-plus@0.1.2 no repository field. npm warn package.json ctype@0.5.2 no repository field. npm warn package.json eyes@0.1.8 no repository field. npm err! peerinvalid package generator-karma not satisfy siblings' peerdependencies requirements! npm err! peerinvalid peer generator-angular@0.3.0 wants generator-karma@~0.3.0 npm err! peerinvalid peer generator-express-angular@0.2.4 wants generator-karma@~0.2.0  npm err! system linux 3.8.0-23-generic npm err! command "/usr/bin/node" "/usr/bin/npm" "-g" "install" "git://github.com/visionmedia/express.git" npm err! cwd /home/guym/dev_env/projects_git/proj/somename npm err! node -v v0.10.10 npm err! npm -v 1.2.25 npm err! code epeerinvalid npm err!  npm err! additional logging details can found in: npm err!     /home/guym/dev_env/projects_git/proj/somane/npm-debug.log npm err! not ok code 0 

edit :

seems epeerinvalid error has nothing have been trying accomplish. globally uninstalled "generaotr-express-angular" , "generator-angular" , worked.

my question

why did unrelated problem affected me? how avoid it?

even though fails, express still installed looks of it.

the reason npm fails because performs sanity check of locally installed modules, , check fails because of invalid peer dependency (explained here). issue might not directly related express, npm doesn't know think assume issue might cause problems , require issue resolved. think any package have installed, not express, have triggered same error.

as found out, removing offending packages solves (another solution might have been update them, provided newer versions fix problem). how got installed in first place, don't know. perhaps installed npm-version didn't yet have peer dependency resolution.