Tracking progress of .wasm fetch

[connorjclark]

The current fetch approach of loading a wasm module allows you to track the progress of the (often large) network resource, and indicate its progress to the user (you just wrap fetch with something like this).

The whole point of this proposal is to make the wasm exports available "statically", so the entire loading phase is made opaque. But I wonder if a dynamic import could somehow provide hooks to track progress?

const wasm = import('some.wasm');

wasm.onProgress(...)

const {exportedFn} = await wasm;

I understand this is not possible with dynamic imports today, so this is probably the wrong place to talk about this idea... In any case, it'd be good to mention "indicate progress" use case as a non-goal, as it's the first thing I thought of (and is a reason I wouldn't make use of this if the binary is large enough).

[annevk]

This seems like a good thing to raise with TC39: https://github.com/tc39/proposals.