New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deno install with import_map.json appears to be broken #15350
Comments
any update on this? I am wondering if I need to rework this pr to avoid using import maps, as currently there is no good way for users to install my package |
I'm running into this as well. This being broken is sort of a big deal. If you want to use a library that forces you to use import maps, you now give up being able to Update/Tangent: I'm also a bit worried seeing the Deno team using import maps for libraries. As the ecosystem grows, if this becomes a common pattern, every consumer of a library, all the way down the dependency chain, will have to start manually maintaining a larger and larger list of mapped imports, and manually investigating which versions work with which dependencies. Maybe a better pattern would be to depend on a default version (so avoiding import maps) and have tooling that can (optionally) override that version with import maps as necessary? |
@andykais A standard way of managing your dependencies is in a |
I have made this third party module https://deno.land/x/wallpal. It is a cli script, so I attempted to install it with
deno prints this output, then exits with
1
.This project has an import map that looks like this:
and imports that look like
It seems that deno is attempting to resolve these imports as if they are local to the wallpal module. These import maps work fine locally, but they fail with
deno install
, so I am inclined to believe there is a bug.deno --version
The text was updated successfully, but these errors were encountered: