is it even sensible to have a configuration like this ```kotlin { wasmJs{ nodeJs() } }``...

# webassembly

[andylamax]

is it even sensible to have a configuration like this

kotlin {
   wasmJs{
      nodeJs()
   }
}

[Robert Jaros]

Of course it is. You can run your K/Wasm application in nodeJS just like K/JS application. You just need to configure nodeJS canary to be able to run application or tests from gradle.
https://github.com/rjaros/kilua/blob/main/kilua/build.gradle.kts#L76-L83

[andylamax]

I see. Are there any benefits for choosing

kotlin {
   wasmJs {         // this
      nodeJs()
   }

   wasmWasi {      // over this??
      nodeJs()
   }
}

[Robert Jaros]

wasi is completely different runtime and needs dedicated libraries. Currently there are almost none (e.g. no coroutines).

[Robert Jaros]

wasmJS on node uses JS runtime, you can use JS interop and most important libraries are available

[andylamax]

I think koitlinx-serialization (version 1.6.2) already added a wasi target

[andylamax]

So, mostly then, we we choose the former due to lack of third party libraries (at the moment)

[Robert Jaros]

You are right

[Robert Jaros]

It probably depends what you want to implement. WasmJS on node allows you to use the large part of JS ecosystem.

[andylamax]

Thank you a lot

[andylamax]

I still have a side question though.

if wasi is a completely different runtime, then what does it mean to have it be declared like this

wasmWasi {
      nodeJs()
   }

[Robert Jaros]

No idea 🙂

[andylamax]

As in, you run wasi (a completely different runtime) inside/from node(a completely different runtime)??

[andylamax]

Seems so confusing at the moment

[Robert Jaros]

I would assume it's something connected with https://nodejs.org/api/wasi.html

[andylamax]

Thanks for the link. Let me go through it

[andylamax]

Well, you are probably right. And if that's the case, I find it so hard (and inconvenient) for the kotlin team to maintain different wasi runtimes through the KGP??

Coz we do have runtimes like (https://github.com/wasmerio/wasmer-java), and I believe there are many more

But that should not make the kotlin team add it in the KGP like so, should it??

wasmWasi {
  wasmerJava() // ??? possible, but why??
}

[Robert Jaros]

Why not? I would be happy to choose one or many supported runtimes with simple DSL.

[andylamax]

I dunno, Coz there are going to be a gazillion of those?

[Robert Jaros]

There is already a gazillion of supported browsers inside the useKarma { } DSL and I find it really nice 🙂

[andylamax]

hahahaha, very true. I find it really nice myself

[Svyatoslav Kuzmich [JB]]

Currently we already have a maintained Node.js support from Kotlin/JS KGP (we needed at least one to run tests without browsers). And now we reuse it for both wasmJs and wasmWasi 🙂

Hopefully, WASI as a standard, would allow you test your code in one runtime, and deploy it to the other.

[andylamax]

Makes sense