Error in outdated after publishing new version #660

Closed
maritz opened this Issue Mar 1, 2011 · 3 comments

Comments

Projects
None yet
2 participants

maritz commented Mar 1, 2011

I just published nohm@0.2.1 and tagged it as latest&stable. Afterwards I uninstalled the nohm@0.2.1 that I had tested via "npm install ." in my nohm directory.
Then I tried "npm outdated" and got this:
https://gist.github.com/848743

Manually installing 0.2.1 from npm works just fine. (npm install nohm@0.2.1)

Did I do something wrong or is there a bug here somewhere?

Owner

isaacs commented Mar 1, 2011

Closed by 3030e72 undefined log message

Owner

isaacs commented Mar 1, 2011

Note: "outdated" just shows you which packages are outdated, it does not install anything. But yes, that log message was an error.

maritz commented Mar 1, 2011

Yep, I use outdated quite frequently. Thanks for the fix! :)

This issue was closed.

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