TC39 Module Harmony
2023-08-23
plaintext logs
prev next
source on github
09:17
<nicolo-ribaudo>

No, I always assumed that the "module instance phase" is equivalent to

import module mod from "m";

// equivalent to

import source _s from "m";
const mod = new Module(_s, {
  importHook: <the import hook from this module>,
  ...<context needed for the import hook>,
});
09:18
<nicolo-ribaudo>
That is, it's not linked but it has the necessary info to then link it (either "here" or "on the other side")
16:10
<Kris Kowal>
That’s interesting. That suggests that we may need to think more rigorously on this, that there may need to be a mechanism to explicitly advance to the linked phase.
16:11
<Kris Kowal>
Either that or put bundlers or module-instance-transfer mechanism at liberty to advance to the linked phase for a module instance by some other means.
16:13
<Kris Kowal>
I’m tentatively assuming we’ll need import.link(mod) for that.
17:00
<Luca Casonato>
I realized during the tc39 tools meeting just now that you also get a form of asset references with module instance imports: import module a from "data:application/javascript,export * from './a.js'";
17:00
<Luca Casonato>
it's very cheaty
17:01
<Luca Casonato>
Well it doesn't actually work because you can't have relative specifiers in data URLs, but it can nearly work