[feature-request] support wasm target

[VladislavSumin]

It is possibly to support wasm target? Coroutines and Compose libraries already have experimental wasm target support

[github-actions]

Thank you for reporting an issue. See the wiki for documentation and slack for questions.

[oshai]

If you have any reference how to add such support to a lib I would be happy to add it. Of course contribution is also welcome.

[Laxystem]

If you have any reference how to add such support to a lib

WASM is a compile target, that similarly to JS, has browser and nodejs - but it also has d8 (no idea what that is tbh).

WASM Support will be very appreciated!

[oshai]

If I understand correctly, our current "native" implementation (writing logs using println) can also work in wasm. So the main thing to add is the gradle configuration. No need for many code changes.

[Laxystem]

Do note that when WASM is out of alpha, it'll likely have interop with other WASM languages, allowing for usage of more complex log libraries than the basic stdout.

Plus, you can use JS console in WASM - it has JS interop.

[oshai]

Which impl do you think is the most appropriate?

[Laxystem]

Which impl do you think is the most appropriate?

I think console, as it supports multiple log levels. However, println delegates to the standard WASM output. To allow for more consistent interop with other languages (when the time comes), I would suggest both - by making one the default and the other an add-on artifact.

The same, btw, applies to println - if you choose to only implement that, interop with JS will be less consistent.

(console supports, iirc, debug, normal/info, warning, and error, while println is only normal/info and error)

[gsteckman]

Kotlin for WebAssembly is now alpha.

[severn-everett]

What's left for this issue?