Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

npm outdated broken? #2557

Closed
donpark opened this Issue · 8 comments

5 participants

@donpark

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

@isaacs npm outdated remains broken in 1.1.37.

@isaacs
Owner

Patch welcome.

@jazzzz

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

@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 referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
@donpark

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

@donpark

This bug was fixed in 1.1.42

@donpark donpark closed this
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.