If you don't want to break the code for people who already are using your library you go and increment the major version: e.g. The reason is that while the software is evolving the API changes rapidly: one day you have these methods and the other day you have those methods and the old ones are gone. When the software is emerging use 0.x.y versions and hat matching will only match the last varying digit ( y). Hat matching may be considered "broken" because it wont update ^0.1.2 to 0.2.0. Notice: When you install a package which has 0 as major level, the update will only install new beta/pr level version! That's because npm sets ^ as default in package.json and when installed version is like 0.1.3, it freezes all major/minor/patch levels.
Notice: Missing major, minor, patch or specifying beta without number, is the same as any for the missing level.
0 kommentar(er)
