3 ms·
The convention is to make a `deps.ts` and re-export what you need. Like this: https://deno.land/x/collections/deps.ts https://deno.land/x/collections/deps.ts I
by mrkurt 6y ago
The convention is to make a `deps.ts` and re-export what you need. Like this: https://deno.land/x/collections/deps.ts https://deno.land/x/collections/deps.ts
I don't find versioned URLs much more difficult to work with than package@<version> though.
- uryga 6y agoi'm wondering if they'll end up adding a 'dependencies.json' to eliminate the boilerplate from 'deps.ts' and to simplify tooling. that'd be revolutionary! ;) jokes aside, i wonder how import-via-url will impact tooling. having to parse arbitrary JS (or even run it, for dynamic imports?) seems like it'd make writing a "list all dependencies" tool much harder than a "dumb" JSON/TOML/whatever file would. though i guess Go does a similar thing, and afaik they're fine
- mrkurt 6y agoWell they do have import maps! I think everyone likes shorthand package names.