[tracker1]

Many node packages will have incompatible api breaks across years of development. More so if your TS types have changed in incompatible ways and you're stuck re-jiggering your code. Can usually resolve in a few days. My advice is to, in general plan on one day a month to upgrade all dependencies to their latest version, which reduces the exposure a lot and makes it easier to deal with than years later. It's worse on front end projects that use node for build tooling.

Ironically, I think the worst libraries for breaking changes are actually the testing libraries themselves. Having to jump 2-3 major versions to update to latest is an exercise in extreme frustration.

I appreciate a lot of what Deno is doing in their direction, though I've felt a few breaking changes along the way there too.