pnpm
Why are some @pnpm/* packages now at version 1000.Y.Z? #9004
Replies: 1 comment 4 replies
-
|
Albeit questionable, they did mentioned it right here in discussions https://github.com/orgs/pnpm/discussions/3837. |
Beta Was this translation helpful? Give feedback.
-
|
Seems a bit weird that the packages I mentioned just recently made this move. Also, instead of being multiplied by 1000 like in the other discussion, it is only multiplied by 100. |
Beta Was this translation helpful? Give feedback.
-
|
That is the answer. |
Beta Was this translation helpful? Give feedback.
-
|
Wow, that discussion is so old, from 2021. I totally forgot about it and came up with the same idea a few weeks ago. |
Beta Was this translation helpful? Give feedback.
-
|
Anthony Fu independently also came up with the same idea and published an article about it: https://antfu.me/posts/epoch-semver |
Beta Was this translation helpful? Give feedback.
-
Some published packages, like
@pnpm/constant,@pnpm/types,@pnpm/config, etc., are now at a major version over 1000? Looking at the changelog and the changesets configuration, I don't understand why or how this happened.Beta Was this translation helpful? Give feedback.
All reactions