It's not a cultural problem. People make mistakes. People don't know what a non-breaking change is, especially those not well versed in refactor work. I don't

It's not a cultural problem. People make mistakes. People don't know what a non-breaking change is, especially those not well versed in refactor work. I don't think Yarn solves any of these problems, tbh. It seems like what we really need is a package manager that tests the api of each package update to make sure nothing in it has broken expectation in accordance with Semver.