3 ms·
Because that is not the convention in the ecosystem - npm mandates the use of semver - if you follow it this can't happen. If you do what you say and pin it dow
by abritishguy 12y ago
Because that is not the convention in the ecosystem - npm mandates the use of semver - if you follow it this can't happen. If you do what you say and pin it down to an exact version then you would have to release an update every week consisting of just a version bump.
- jessaustin 12y agoDon't stop there: think it all the way through! Breaking changes lead to version bump releases, whether the module follows semver or not. https://news.ycombinator.com/item?id=8244888 https://news.ycombinator.com/item?id=8244888 Do you mean to imply that breaking-change frequency should stay below some particular maximum value? That argument is completely unrelated to the use or disuse of semver.