Is there a way to handle subpath imports within a library?
I'm trying to convert a library package to work with deno.
Internally, the package makes a bunch of (different) subpath imports from another library of ours.
If this were an application making these imports, I'd just use an import map. However, the docs are pretty clear that, for a library, you should create a
Is there a pattern for import map style mappings, for a library?
Internally, the package makes a bunch of (different) subpath imports from another library of ours.
If this were an application making these imports, I'd just use an import map. However, the docs are pretty clear that, for a library, you should create a
deps.tsdepsIs there a pattern for import map style mappings, for a library?
