Created
April 24, 2012 08:45
-
-
Save trodrigues/2478000 to your computer and use it in GitHub Desktop.
union install error
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
% npm install union | |
npm http GET https://registry.npmjs.org/union/0.3.0 | |
npm http 200 https://registry.npmjs.org/union/0.3.0 | |
npm http GET https://registry.npmjs.org/union/-/union-0.3.0.tgz | |
npm http 200 https://registry.npmjs.org/union/-/union-0.3.0.tgz | |
npm http GET https://registry.npmjs.org/pkginfo | |
npm http GET https://registry.npmjs.org/qs | |
npm http 304 https://registry.npmjs.org/pkginfo | |
npm http 200 https://registry.npmjs.org/qs | |
npm ERR! error installing [email protected] | |
npm ERR! error installing [email protected] | |
npm ERR! error rolling back [email protected] Error: UNKNOWN, unknown error '/Users/trodrigues/code/website/node_modules/union/node_modules/___qs.npm/package' | |
npm ERR! Error: ENOENT, no such file or directory '/Users/trodrigues/code/website/node_modules/union/node_modules/pkginfo/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! <[email protected]> | |
npm ERR! | |
npm ERR! System Darwin 11.3.0 | |
npm ERR! command "node" "/usr/local/bin/npm" "install" "union" | |
npm ERR! cwd /Users/trodrigues/code/website | |
npm ERR! node -v v0.6.11 | |
npm ERR! npm -v 1.1.1 | |
npm ERR! path /Users/trodrigues/code/website/node_modules/union/node_modules/pkginfo/package.json | |
npm ERR! code ENOENT | |
npm ERR! message ENOENT, no such file or directory '/Users/trodrigues/code/website/node_modules/union/node_modules/pkginfo/package.json' | |
npm ERR! errno {} | |
npm ERR! | |
npm ERR! Additional logging details can be found in: | |
npm ERR! /Users/trodrigues/code/website/npm-debug.log | |
npm not ok |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
as a personal note, updating npm and clearing it's cache fixes this problem