We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Version: Deno 1.41.3
A single ../ in the path value for "importMap" inside deno.json config file will output error: Loading unprepared module when using deno run.
../
"importMap"
deno.json
error: Loading unprepared module
deno run
Minimal reproducible example:
$ cat main.ts import '~/shared/models.ts'; $ cat deno.json { "importMap": "../import_map.json" } $ cat ../import_map.json { "imports": { "~/shared/": "./shared/" } } $ cat ../shared/models.ts export class Model {}
This happens since 1.41.1 but I decided to build Deno from source to find the exact commit that caused this: 6567dc9
Running the debug build will trigger a panic at this location:
deno/cli/args/import_map.rs
Lines 77 to 81 in ae52b49
The current workaround is to use "imports" in the config file or to use the --import-map flag.
"imports"
--import-map
The text was updated successfully, but these errors were encountered:
Thank you so much @NeKzor for workaround 🎉 ❤️ It saved me literally hours 🍺
Sorry, something went wrong.
Fixed a couple weeks ago in #23602
dsherret
No branches or pull requests
Version: Deno 1.41.3
A single
../
in the path value for"importMap"
insidedeno.json
config file will outputerror: Loading unprepared module
when usingdeno run
.Minimal reproducible example:
This happens since 1.41.1 but I decided to build Deno from source to find the exact commit that caused this: 6567dc9
Running the debug build will trigger a panic at this location:
deno/cli/args/import_map.rs
Lines 77 to 81 in ae52b49
The current workaround is to use
"imports"
in the config file or to use the--import-map
flag.The text was updated successfully, but these errors were encountered: