It's not a frontend problem but a JS-ecosystem problem. Happens in the backend too. The JS landscape is an absolute mess where dependencies have dozens if not

It's not a frontend problem but a JS-ecosystem problem. Happens in the backend too. The JS landscape is an absolute mess where dependencies have dozens if not hundreds of other dependencies. As an example, this is the dependency graph of Platformatic (a Node framework based on Fastify): https://npmgraph.js.org/?q=platformatic#zoom=h https://npmgraph.js.org/?q=platformatic#zoom=h Each of those dependencies could be abandoned at any moment. Even huge dependencies like Axios or Express seemed to have been abandoned at one point. And then each dependency is ruled by whatever their maintainers think is right. Just the other day a dependency I use in prod with aprox 25M downloads per week (React is aprox 26M) and used by 10M Github repos decided it was ok to drop support for Safari versions from about 3 years ago. It's just insane considering Safari has +50% mobile market share in the US.