andylamax
02/16/2023, 9:15 AMkotlin {
js(IR) {
browser()
binaries.executable()
}
}
instead of
kotlin {
wasm {
browser()
binaries.executable()
}
}
this seems a bit offOleksandr Karpovich [JB]
02/16/2023, 9:36 AMandylamax
02/16/2023, 3:00 PMandylamax
02/16/2023, 3:04 PMOleksandr Karpovich [JB]
02/16/2023, 3:36 PMboth wasm implementations in both k/js and k/wasm targets??I’m not sure I completely understood your question. In case of compose-web-canvas with k/js only skiko is compiled to wasm. The rest (compose-runtime, compose-ui, etc) is compiled to js. With k/wasm we can compile all compose libs to wasm + use skiko already compiled to wasm. __ If you’re asking “why to keep compose-web-canvas k/js and k/wasm targets if k/wasm does the same?” For now, k/wasm requires GC flag enabled in a browser. Unless keeping and maintainig both targets requires a lot of efforts, I think we would keep both targets.
andylamax
02/17/2023, 7:15 AMandylamax
02/17/2023, 7:16 AM