![]() The change caused a runtime error that prevented users from performing core actions on our application. With the power of semantic versioning, our production build introduced a new dependency patch that contained a hidden, breaking change. Our production build at C2FO, like most node projects, involves an npm install command during the process. Nothing stops a developer from making a breaking change during a bug fix. Unfortunately, trusting open source developers can be a problem. The catch with NPM and semantic versioning is that we have to trust the developers who update the code to do the right thing. ![]() ![]() It provides flexibility for the package developer to make features and bug fixes without negatively affecting the consumers with a major (breaking) change. NPM also provides a ~ substitute if we only want patch modifications. The ^ means that any time we run npm install again, npm will only update or dependency if there is a minor or patch change in the semantic versioning.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |