Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Check for rc / beta / alpha #174

Open
alecmev opened this issue Aug 14, 2016 · 3 comments · May be fixed by #347
Open

Check for rc / beta / alpha #174

alecmev opened this issue Aug 14, 2016 · 3 comments · May be fixed by #347

Comments

@alecmev
Copy link

alecmev commented Aug 14, 2016

This wouldn't be a good default, of course, but would be nice to be able to check for new[-er] rc / beta / alpha releases. Webpack 2, for example, has been in beta for 9 months now, with a fresh release every week or so, and I'd like to keep up with the same ease as I'm able to with regular releases.
@LinusU
Copy link
Collaborator

LinusU commented Aug 14, 2016

I agree, nice feature to have. Pull requests welcome 👍

@vith
Copy link
Contributor

vith commented Jun 7, 2018

This wouldn't be a good default

I disagree, I think this absolutely should be default for dependencies whose installed versions are beta/etc.

At present, npm-check is silent about my babel deps. npm outdated shows them:

❯ npm outdated
Package                                           Current          Wanted         Latest
@babel/cli                                  7.0.0-beta.46   7.0.0-beta.49  7.0.0-beta.49
@babel/core                                 7.0.0-beta.46   7.0.0-beta.49  7.0.0-beta.49
@babel/plugin-proposal-object-rest-spread   7.0.0-beta.46   7.0.0-beta.49  7.0.0-beta.49
@babel/preset-env                           7.0.0-beta.46   7.0.0-beta.49  7.0.0-beta.49

and a yarn upgrade upgraded them.

But I was in the habit of only checking with npm-check so I overlooked these upgrades for a long time.

@alecmev
Copy link
Author

alecmev commented Jun 8, 2018

I'm fully satisfied with yarn upgrade-interactive --latest these days.

@novascreen novascreen linked a pull request Jun 23, 2019 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Take all prerelease tags into account novascreen/npm-check
3 participants
@LinusU @alecmev @vith