2 ms·

Hmm, I don't agree. I see Deno's package.json support as a pragmatic solution to interact with the rest of the world, but for my current use case (command line

Hmm, I don't agree. I see Deno's package.json support as a pragmatic solution to interact with the rest of the world, but for my current use case (command line tools, switching over from Python) the npm registry is quite irrelevant, but the ability to directly import via URL is a real killer feature (also compared to Python). (edited)

illiarian 4y ago
> the direct URL import is vastly superior to external package managers. This is a tooling/ecosystem issue. E.g. in Elixir where the package manager is a part of the distribution, one-file scripts with dependencies are easy: https://fly.io/phoenix-files/single-file-elixir-scripts/ https://fly.io/phoenix-files/single-file-elixir-scripts/
- flohofwoe 4y ago
  Well yeah, but Deno is a tool and ecosystem, just a different one from Node.js and NPM :)
  - illiarian 4y ago
    So it could easily provide the same functionality if it so chose :)