`deno vendor`: help with import_map.json changes from deno.land to jsr?
Hi - I'm hoping to get some guidance of best practices of migrating a (n admittedly complicated) import_map.json file from using https://deno.land/std@0.224.0 to
Our import map at Quarto currently contains entries like this:
We use this syntax because it allows us to do imports in our TS code like this:
This allows our import map to not worry about which of the
My specific problem is I'm having a hard time converting that to a
If I maintain the trailing
But if I switch to an import_map statement like
then it seems that I need to declare each of the imports (tar, zip, etc) separately in the import map itself. That would be a big bummer and a source of ongoing maintenance toil for us, because the import_map will become much more brittle than before. Is there a way to import from jsr and retain the flexibility with paths we used to have in import maps and
jsrjsr Our import map at Quarto currently contains entries like this:
We use this syntax because it allows us to do imports in our TS code like this:
import { Tar } from "archive/tar.ts";import { Tar } from "archive/tar.ts";import { Zip } from "archive/zip.ts";import { Zip } from "archive/zip.ts";, etc.This allows our import map to not worry about which of the
tar.tstar.ts, zip.tszip.ts are going to be ultimately imported in our code.My specific problem is I'm having a hard time converting that to a
jsrjsr import, sayIf I maintain the trailing
// in the syntax, I get a failure like this when calling deno vendordeno vendor:But if I switch to an import_map statement like
then it seems that I need to declare each of the imports (tar, zip, etc) separately in the import map itself. That would be a big bummer and a source of ongoing maintenance toil for us, because the import_map will become much more brittle than before. Is there a way to import from jsr and retain the flexibility with paths we used to have in import maps and
deno vendordeno vendor? Thanks for the help!
