This is a conceptual hack to avoid considering the state of the ecosystem.
Think of software like a living being, not like a statue etched in stone (although even statues etched in stone degrade).
It’s 2012 all over again: “churn makes things better! BTW, what should we be using this week?”
People still build 3 tier apps, and web farms. It’s eternal 1997.
Maybe people shouldn't start software projects if there isn't a "can leave it here unmaintained" milestone within sight.
It's because these projects have tons of dependencies and moving parts which tend to break themselves (often for very little reasons) so of course it's going to affect upstream.
The software you listed are usually mostly self-contained or rely on stable projects.
There is no such thing as "stability" in the Node.js ecosystem (which isn't javascript itself).
Nodejs is the new Java jar dependency hell.
Maybe package the entire project into a docker container so that people can download and run the pile of dependencies in one step.
It is not a nodejs specific problem, every software with dependencies has it. (some more, some less)