Dear JS ecosystem, I love you, but you have a dependency management problem when it comes to the Web, and the time has come for an intervention.

Lea Verou

JavaScript dependency management on the web is fundamentally broken compared to other ecosystems. While Node.js and other platforms treat dependencies as first-class citizens, web developers must choose between fragile workarounds: deploying node_modules directly (security risk), using CDNs (reliability issues), or adopting bundlers for basic needs. Import maps exist but require HTML templating, manual mapping of every transitive dependency, and still need URLs to resolve to. The ecosystem has normalized this complexity, but it harms both newcomers and the platform's architecture. Proposed solutions include external import maps, HTTP header-based resolution, treating specifiers as a URL type, and server-side dependency resolution to make web dependencies truly first-class without requiring bundlers.

Web dependencies are broken. Can we fix them? • Lea Verou

But won’t import maps solve all our problems?

As a newbie developer learning reactjs frontend development, I:
<ul>
<li>Read the entire post out of curiosity.</li>
<li>Feeling like an 10+years of experience libraries developer(even though didn’t understand 98% of what was written)</li>
<li>Still Enjoyed reading a lot 💖</li>
</ul>
Great post (Not like i know anything…).👍

The web is a mess. The JS world is pure chaos, but it’s what we have… I hoped web assembly would replace it but it’s not happening any time soon if at all.