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

`npm bugs` should print something if it can't open the website #2684

Closed
mcavage opened this Issue Aug 7, 2012 · 3 comments

Comments

Projects
None yet
5 participants

mcavage commented Aug 7, 2012

I ran that from an ssh'd session, inadvertently, so obviously it couldn't 302 my browser. Should dump something to stderr to indicate npm couldn't do so.

fritx commented May 5, 2014

isn't this solved?

Contributor

thomblake commented Jul 24, 2014

I think this might be solved.

Just overrode open to false, and npm bugs helpfully gave me the following output:

$ npm bugs
npm ERR! Error: Command failed:
npm ERR!     at ChildProcess.exithandler (child_process.js:637:15)
npm ERR!     at ChildProcess.EventEmitter.emit (events.js:98:17)
npm ERR!     at maybeClose (child_process.js:743:16)
npm ERR!     at Socket.<anonymous> (child_process.js:956:11)
npm ERR!     at Socket.EventEmitter.emit (events.js:95:17)
npm ERR!     at Pipe.close (net.js:465:12)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Darwin 13.3.0
npm ERR! command "/usr/local/Cellar/node/0.10.26/bin/node" "/usr/local/bin/npm" "bugs"
npm ERR! cwd /Users/tblake/github/npm
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! code 1
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/tblake/github/npm/npm-debug.log
npm ERR! not ok code 0
Contributor

othiym23 commented Sep 22, 2014

Closing as resolved.

@othiym23 othiym23 closed this Sep 22, 2014

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