The web development community faces significant issues with dependency management. Unlike environments like Node.js, Python, or Rust, where adding dependencies is straightforward, the web platform relies heavily on bundlers like Webpack and Rollup. This reliance complicates what should be a simple process. For developers, particularly newcomers, the experience of adding a library often becomes overwhelming due to the necessity of choosing a bundler and navigating its configuration. The article emphasizes that dependency management should be more integrated into the web platform itself, rather than requiring advanced tools. Importing dependencies directly from the node_modules directory isn’t practical. It poses security risks and violates encapsulation principles, as internal paths of packages shouldn’t be exposed. The alternative—using public CDNs for importing libraries—carries its own risks, including potential security vulnerabilities and reliance on third-party domains. Issues like unavailability during outages can disrupt development and deployment, making it an unreliable solution. The author argues for a more coherent approach to dependency management on the web, one that doesn’t force developers to deal with complex bundling processes. Such a system should allow for straightforward installation and importation of packages without additional hurdles. The current state leads to frustration and inefficiencies in the development workflow, especially for those new to the ecosystem.