I believe the long term solution to the issues you raised is import maps: https://github.com/WICG/import-maps https://github.com/WICG/import-maps It's an upcom

I believe the long term solution to the issues you raised is import maps: https://github.com/WICG/import-maps https://github.com/WICG/import-maps It's an upcoming feature on the browser standards track gaining a lot of traction (deno already supports it), and offers users a standardized way to maintain the decoupling that you mentioned, and allows users to refer to dependencies in the familiar bare identifier style that they're used to from node (i.e. `import * as _ from 'lodash'` instead of `import * as _ from 'https://www.npmjs.com/package/lodash'` https://www.npmjs.com/package/lodash'`). I imagine tooling will emerge to help users manage & generate the import map for a project and install dependencies locally similar to how npm & yarn help users manage package-lock.json/yarn.lock and node_modules.