Some random ideas on NPM update policies
I’ll start saying that what follows is the kind of stuff that I’m always a bit afraid to share because I mostly expect indifference or criticism, but I guess that there’s no point on writing about it if it’s not shared afterwards.
For a few weeks I’ve been thinking that, while semantic versioning is awesome, in some situations is not enough. Not everyone follows it, people break the convention accidentally, and we lack tools to manage the complexity that arises from it.
So I wrote a draft of a proposal that intends to surface some of the hidden complexity behind dependencies management to make it easier to tame, with the hope that it can help to reduce problems due to dependencies’ breaking changes.
If you are interested in JavaScript or NodeJS development, I’d love to have some input from you (this also includes the criticism I always fear, as long as it’s constructive 🤓)
You must log in or register to comment.
Have you thought about providing this for some dependency updating solution like renovatebot?
Hi. I think that before introducing this for bots, it should be baked in package managers in order to gain traction (this idea, or something along the same lines).
Good job on thinking about this topic critically. We need these thoughts experiments even if they don’t result in revolutionary change.
Thank you, I really appreciate people taking their time to read these ideas :) .