I went the route of strictly following semantic versioning & now have packages > v20. I iterate quickly & often have breaking changes. The aws packages, having version > 100, normalizes this pattern.
A heralded major version update seems like a marketing concern. I still have bad memories lingering of upgrading a projects Rails from from v2-v3 or Angular 7-8. This indicates that the releases are too big, indicating that the libraries/frameworks are too big.
Smaller libraries tend to not have the marketing concerns that a famous framework has, so having a high major version would be ok...
1 comment
[ 3.2 ms ] story [ 17.5 ms ] threadA heralded major version update seems like a marketing concern. I still have bad memories lingering of upgrading a projects Rails from from v2-v3 or Angular 7-8. This indicates that the releases are too big, indicating that the libraries/frameworks are too big.
Smaller libraries tend to not have the marketing concerns that a famous framework has, so having a high major version would be ok...