Most of modern software applications has dependency on many packages, each one with its own development flow in different stages. You may have heard about "dependency hell", which is where you are when you can't upgrade your project without the huge risk of breaking the dependency tree.
With the idea of defining a standard way of naming each version and tracking when there are new breaking changes, Semantic Versioning was created as a simple set of rules and requirements that dictate how version numbers are assigned and incremented.
This is how it looks like:
And this is how you should upgrade:
When using a package manager, you can reference a fixed dependence version or a dynamic one (E.g. give me always the latest package version). In the second case, you can do it with the following rules:
ππ
Thanks a lot for reading! Remember this post is part of βFrom Zero to Hero: Painless way of building a great Javascript libraryβ series.
See you next time at: βπΉ Part 3 - Making your Javascript library in less than five minutes with Pika.β !
Subscribe for latest updates
Sign Up for our newsletter and get notified when we publish new articles for free!