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!
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 :)