Skip to content

npm outdated broken? #2557

Closed
donpark opened this Issue Jun 22, 2012 · 8 comments

5 participants

@donpark
donpark commented Jun 22, 2012

In versions since 1.1.30, npm outdated outputs nothing yet npm update updates many modules for both global and local modes.

@syamanaka

1.1.25 is the last version that npm outdated worked for me. Version 1.1.26 displayed cb() never called!. The error was fixed in 1.1.27, but now it doesn't output anything. Still not working in 1.1.35.

@donpark
donpark commented Jul 11, 2012

@isaacs npm outdated remains broken in 1.1.37.

@isaacs
npm member
isaacs commented Jul 12, 2012

Patch welcome.

@jazzzz
jazzzz commented Jul 12, 2012

The issue is due to the commit e6a7e44. Reverting it makes outdated work again, however I don't know what this change fixed in the first place.

@Sembiance

I can confirm that reverting the change jazzzz mentioned does indeed fix outdated. Perhaps the cb_ is calling process.exit() before the .write() is finished?

@jazzzz
jazzzz commented Jul 13, 2012

@Sembiance if I remember correctly, the write method from utils/output.js does not do anything when no callback is provided. Maybe this should be fixed.

@donpark
donpark commented Jul 13, 2012

I'll submit a pull request when Github lets me create one instead of barfing 404.

@isaacs isaacs added a commit that referenced this issue Jul 16, 2012
@donpark donpark fix broken outdated cmd #2557 03666c2
@donpark
donpark commented Jul 19, 2012

This bug was fixed in 1.1.42

@donpark donpark closed this Jul 19, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.