Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Bug in npm badges

See original GitHub issue

Again. 😄

@babel/core is cyan, but shouldn’t be, because it is latest.

The cyan should be only if non-latest dist-tag is passed, no matter it is scoped or not.

Issue Analytics

State:
Created 5 years ago
Comments:15 (15 by maintainers)

Top GitHub Comments

2reactions

tunnckoCorecommented, Aug 25, 2018

Babel is specific case, that was said…

But i won’t continue, cuz i’m seeing that other 👍 all the time, so i will fold that. ;/

2reactions

amiocommented, Aug 25, 2018

Consider @babel/core’s case, I think latest doesn’t always mean “stable” or “best” (maybe “recommended”?).

In our cases, the cyan color doesn’t (shouldn’t) mean stable or unstable, just like the orange doesn’t say it’s unstable (we use a lot 0.x packages in production).

semColor() is meant to reflect semver’s convention:

Orange => the MAJOR version is 0
Cyan => the version has pre-release meta
Blue => the version’s MAJOR > 0 and doesn’t include any pre-release tag, seems like stable.

If there’s a platform specific case, it should be handled in services’s live function, other than semColor().