Great Article, thank you :)
I saw that break changes happens In a minor version.
One of the packages is antd. I used a version 4.18.5 of antd.
Its latest version is 4.24.7. I tried to upgrade the version for new features but there were break changes, so, I couldn't. Now, I'm using it as a fixed version. (At least, I could use tilde though). Are there better options in this sitation that I can take?
Hi SeongKuk! Ideally, package mantainers should not push breaking changes in a minor version. Sometimes this happens and we can use a fixed version as a quick fix while we prepare our project to work with the newest package version.
This was out of the scope of this article, but since we depend on other's packages when using npm, we cannot always verify if the maintainers are following SemVer correctly :( we can do our part though, and be prepared when things don't go as planned :) Thank you for reading!
Great Article, thank you :)
I saw that break changes happens In a minor version.
One of the packages is
antd. I used a version4.18.5ofantd.Its latest version is
4.24.7. I tried to upgrade the version for new features but there were break changes, so, I couldn't. Now, I'm using it as a fixed version. (At least, I could use tilde though). Are there better options in this sitation that I can take?Hi SeongKuk! Ideally, package mantainers should not push breaking changes in a minor version. Sometimes this happens and we can use a fixed version as a quick fix while we prepare our project to work with the newest package version.
This was out of the scope of this article, but since we depend on other's packages when using npm, we cannot always verify if the maintainers are following SemVer correctly :( we can do our part though, and be prepared when things don't go as planned :) Thank you for reading!
Thanks for reply :)