> especially given a community so willing to publish backwards incompatible changes come hell or high water This triggers me. I feel like I dealt with this iss

> especially given a community so willing to publish backwards incompatible changes come hell or high water This triggers me. I feel like I dealt with this issue almost on the daily (ok, ok -- weekly) until we fully moved to yarn and started freezing the lockfile [0] with: yarn --frozen-lockfile It really is ridiculous. And even with yarn, I still have multiple resolutions [1] in our package.json files due to breaking changes in patch versions without a fix. [0]: https://yarnpkg.com/lang/en/docs/cli/install/ https://yarnpkg.com/lang/en/docs/cli/install/ [1]: https://yarnpkg.com/lang/en/docs/selective-version-resolutions/ https://yarnpkg.com/lang/en/docs/selective-version-resolutio...