Support deno run resolving bare specifiers with import map

[leighmcculloch]

Proposal

Support deno run resolving bare specifiers with the import map.

For example:

If the deno.json file contains an import map that maps lume/ to https://deno.land/x/lume@v1.18.1/:

{
  "imports": {
    "lume/": "https://deno.land/x/lume@v1.18.1/"
  }
}

It be possible to reference the bare specifier with deno run:

deno run lume/cli.ts

Instead of:

deno run https://deno.land/x/lume@v1.18.1/cli.ts

Why

Today bare specifiers are interpreted inconsistently by deno run and an import. imports with bare specifiers interpret them using an import map and relative paths must be prefixed with ./. deno run however treats a bare specifier as a relative path.

This prevents developers from conveniently referencing versions in an import map in deno run commands, or in deno tasks. It is easy to accidentally use the wrong version when running a tool with deno run when the project is configured for a different version.

It is possible to work around this by piping an import to the deno run command, but this is not intuitive. For example:

echo "import 'lume/cli.ts'" | deno run -

[dsherret]

This was just implemented for deno info. I think it makes sense to do for all sub commands.

#19781

[bartlomieju]

PRs are welcome. Would be great to ship it in v1.36 next week.

[oscarotero]

This would be awesome. I've requested something similar in #14066 without luck :)