How ImportObject works with ESM? about esm-integration HOT 4 CLOSED

The current default output of Emscripten isn't really ESM-compatible; it's expecting to be instantiated manually by a containing .js glue file and so I think there would be more issues than just the naming of env. Emscripten has a lot of flags for adapting output, though; @kripken / @dschuff, is there anything at the moment that is more ESM-compatible?

from esm-integration.

Sounds like the context here is that ./ prefixes would make sense when the wasm imports an ES module for env/global? Makes sense to me if so.

For emscripten js output the general goal is to have the "modularize" option emit an ES module (right now it emits a function with clear imports/exports but is not ESM yet). I'm not sure how that would work with it being imported by the wasm, I don't think anyone has had time to think about that yet.

from esm-integration.

Emscripten is an example, currently nobody considers that.

Also cc @dcodeIO @ballercat

from esm-integration.

@xtuc I see you reopened this, but I'm not sure what issue needs to be resolved here. This seems like an issue with module resolution algorithms. Is that correct? If it is, then that is an issue being handled in other WGs and would be outside of the scope for this WG.

Closing for now, but if the issue is something in scope for this proposal we can reopen.

from esm-integration.