Is there any plan to do something like <https://yo...
# webassembly
r
Is there any plan to do something like https://youtrack.jetbrains.com/issue/KT-47038/KJS-MPP-Split-JS-target-into-JsBrowser-and-JsNode for WASM? I can see how the JS version might have backward-compatibility difficulties, but that seems like less of an issue while WASM is still experimental. It would be really helpful especially in a library setting to be able to have different source-sets for browser/node/d8 without needing to manually define target attributes that consumers then need to also declare.
plus1 3
a
r
I'm not sure if that fully covers what I was thinking. In a world where wasm-js and wasm-wasi are different, is wasm-js limited to browser use-cases or does it still have node as an option? If the latter, then I still want a further split between browser and node within the wasm-js target.