Replies: 1 comment
-
2.0.0-next.132 has been downloaded 3,000+ times this week while 2.0.0 has been downloaded 134. Any idea how those 134 people end up getting that version while everyone else gets the correct version? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
According to the SemVer specification
2.0.0
has a higher precedence than2.0.0-next.129
but according to the npm registry2.0.0
was released at2020-10-16T22:58:56.546Z
while2.0.0-next.129
was released at2022-04-15T12:50:36.481Z
.Since both
latest
andnext
point to2.0.0-next.129
I'm assuming this isn't on purpose.Could
[email protected]
be deprecated to warn users about this or could a new version with a higher precedence be published?Beta Was this translation helpful? Give feedback.
All reactions