2 ms·
have to specify exact dependency versions in my package.json, and almost every time I update one of them, something goes wrong. That's where semantic versionin
by untog 11y ago
have to specify exact dependency versions in my package.json, and almost every time I update one of them, something goes wrong.
That's where semantic versioning comes in. Most libraries follow it - if the major version number changes, it's a breaking change. If it doesn't, you're safe to upgrade.
- Touche 11y agoSemantic version doesn't solve compatibility problems, it just makes it more transparent. In some ways semver encourages breaking changes that otherwise might be avoided because, how, a major version bump gives you sufficient warning. There are some major libraries that are on version 15 or greater... there's nothing good from a user's perspective about having a library they use do a major breaking release every other month. What's worse is many libraries take advantage of "it's the wild west until 1.0" rule in semver and simple never release a 1.0.