TC39 Module Harmony on 2024-06-16

04:41	<guybedford>	guybedford I was talking with Luca and we have different understanding of how module identity is preserved across cloning. Do you expect this to be true or false? `import source x from "./x.js"; await import(x) === await import(structureClone(x));` My current best understanding of how this might work would be that the objects would have different equality, but because the underlying keys are identical, the instances will be identical. That is, `await import.source(x) === x` but `await import.source(structuredClone(x)) !== x`. In terms of GC, the module registry is not currently clearable. If we want to permit that for hosts, that's maybe a separate discussion, involving a `loader.delete(key)`?
05:23	<guybedford>	maybe it's `import.unref(specifier)` or similar...?
08:31	<Rob Palmer>	Well done to everyone who contributed to this article https://thenewstack.io/how-javascript-is-finally-improving-the-module-experience/
08:31	<nicolo-ribaudo>	(I didn't even remember that she interviewed me for it 😅)