> You create the import map by figuring out what dependencies you want to use and crafting it Ah yes. Truly the same amount of effort as package.json. How exa

> You create the import map by figuring out what dependencies you want to use and crafting it Ah yes. Truly the same amount of effort as package.json. How exactly do you figure out all dependencies (including transitive ones) and "craft" that? Edit TIL you can install as many versions under different names as you want with npm: https://medium.com/weekly-webtips/how-to-install-multiple-versions-of-the-same-package-in-npm-71c29b12e253 https://medium.com/weekly-webtips/how-to-install-multiple-ve... > This is not some grand conspiracy like so many replies seem to be trying to imply. There's no conspiracy. All the awkward workarounds with tedious manual steps to recreate a package.json "dependencies" field are frankly laughable. Deno should bite the bullet and automate this since they already have the dependency resolution built in. No need to "craft" anything.