Dynamic import module is not found when created after the application started.

[jespertheend]

To reproduce, save the following as foo.ts and run deno run -A foo.ts

await Deno.writeTextFile("bar.ts", "export const bar = 'bar'");

const {bar} = await import("./bar.ts");
console.log(bar);

This results in

error: Uncaught (in promise) TypeError: Module not found "file:///.../bar.ts".

Running it a second time works as expected.

---

A workaround is to make the import not statically analysable:

await import("" + "./bar.ts");

But this causes you to lose type info for bar.ts. You can cast it, but it gets a bit tedious:

const {bar} = await import("" + "./bar.ts") as typeof import("./bar.ts");

especially when using JSDoc:

const {bar} = /** @type {import("./bar.js")} */ (await import("" + "./bar.js"));

[nayeemrmn]

This behaviour is intended, we actually discussed it in #17697 (comment) :-)

[jespertheend]

Ah I see 😅
I guess I was a bit too focused on not having it load on startup there. I wasn't aware this was part of the same issue.

[waugh]

So Deno is not designed to comply with ECMAScript, which specifies the meaning and effect of a dynamic import?