Heyo! Anyone in here able to advise on how I might go about adding

wasm32

support for a library of mine; secure-random? It's the only platform not supported currently and I've no clue where to start 😢 Issue Ticket

Teaser (reminder) of this week https://twitter.com/bashorov/status/1620827351356674048

The teaser of the week will come soon, and now you can try to guess what it is about. https://twitter.com/bashorov/status/1622730172548935680

It gotta be

Composy

It’s not actually a teaser teasered before 🌚, but anyway, Good News: https://twitter.com/bashorov/status/1623331214638690304

Hi all! I've been playing with the new Kotlin/Wasm stuff. Very exciting 🙂 One question... It seems the gc Chrome flag (chrome://flags/#enable-webassembly-garbage-collection) isn't in 109 but in 110. But maybe I'm doing something wrong. Anyone know?

Is it a filed/known issue that

wasmBrowserRun

hard codes a default browser exec of

google-chrome-canary

?

Is there any chance we could avoid to have

kotlin-js-store/yarn.lock

generated when not using JS dependencies in our Kotlin/Wasm projects? I guess I am not the only one using Kotlin/Wasm to avoid dealing with the crazy JS ecosystem so getting that thing generated (and expected ti be committed for apps I think) by default is a bit irritating.

So from my understanding the new WASM backend is no longer using LLVM… If not, then what is it using? How is Kotlin creating wasm file?

Has anyone had any success getting Kotlin/Wasm to run on the Wasmer runtime? If you have I would love to know

@David Herman Do you have any plan to support Kotlin/Wasm in https://github.com/varabyte/kobweb?

Hey guys, did anyone manage to incorporate lazycolumn or column to be scrollable vertically? For me it doesn't seem to work even using vertical scroll modifier for column

The teaser of the week! 😉 https://twitter.com/bashorov/status/1625437131706363904

Is there some highlight of what is or isn't currently supported by WASM backend? IIRC things like try-cache were not on the first public showcase? But if it can run Compose I guess it's pretty complete right now.

One more teaser for this week (live demo) https://twitter.com/bashorov/status/1625958156189794313 Enjoy!

I tried on chrome-dev Android version 112. Works but the touch events are really slow/laggy. Animation works laggy too. Firefox on Android nightly 112, didn't work

I have the following setup in

build.gradle.kts

wasm {
        browser()
        binaries.executable()
    }

with a single

index.kt

fun main() {
  println("works")
}

when I run

./gradlew wasmBrowserDevelopmentRun

, it fails with

Module build failed: UnhandledSchemeError: Reading from "node:module" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.

Full error log is in thread. But how do I successfully run this test app??

Just saw that Kotlin/WASM is now a big thing. I spent most of last night porting my JVM project to WASM so that I could visualize the data I've been working with! I made a color LUT generator - this is a visualizer for what the raw output of the generated LUT looks like, before we start patching it up :)

FYI Go is going to support WASI out of the box. https://github.com/golang/go/issues/58141

Hi there, is there an example on how to create a WASM library that can be used from Node.js? Just starting to get an idea of what is possible with WASM… Like, would using WASM make sense if I want to do computation-heavy things on Node? Probably that would require the use of Node workers, wouldn’t it?

No teasers this week, but I have a question for you: https://mobile.twitter.com/bashorov/status/1628516357686849538

Hey, I tried to run https://github.com/linux-china/kotlin-wasm-node-demo after changing the version to

1.8.20-Beta

, but was not able to. Basically, the command

~/.gradle/nodejs/node-v19.6.0-darwin-x64/bin/node --experimental-wasm-gc ~/kotlin-wasm-node-demo/build/js/packages/kotlin-wasm-node-example-wasm/kotlin/kotlin-wasm-node-example-wasm.mjs

failed with the following error message:

file://~/build/js/packages/kotlin-wasm-node-example-wasm/kotlin/kotlin-wasm-node-example-wasm.uninstantiated.mjs:140
        const wasmModule = new WebAssembly.Module(wasmBuffer);
                           ^

CompileError: WebAssembly.Module(): Compiling function #16:"kotlin.collections.IteratorImpl.hasNext" failed: i32.trunc_f64_s[0] expected type f64, found call_ref of type i32 @+14179
    at instantiate (file://~/kotlin-wasm-node-demo/build/js/packages/kotlin-wasm-node-example-wasm/kotlin/kotlin-wasm-node-example-wasm.uninstantiated.mjs:140:28)
    at async file://~/kotlin-wasm-node-demo/build/js/packages/kotlin-wasm-node-example-wasm/kotlin/kotlin-wasm-node-example-wasm.mjs:3:17

Is this a known issue?

Just another question: what do I have to do in order to add a function or a value to the WASM exports? I inspected the .wat file and the only exports I could find were “__init” and “memory” .

Sorry for spamming this channel, but could you please provide more information on whether Long & ULong are already compiled correctly? I tried to add a parameter with such type to an exported function, but this leads to the following: • JS-related warning is emitted:

Exported declaration uses non-exportable parameter type: ULong

-> seems to be ignorable • .wat file no longer exists • WASM Instance can be instantiated in nodeJs & function called for Long -> for ULong, WASM Instance can not be instantiated due to

Compiling function #656:"fibonacci__JsExportAdapter" failed: type error in branch[0] (expected structref, got i64) @+55427

(function signature looks like

fun fibonacci(n: ULong, a: ULong, b: ULong): ULong

) Also, if I try to add a default value for the parameters

a

&

b

in the ULong case, I get another error:

Duplicate export name 'fibonacci' for function 656 and function 657 @+14021

... Any ideas?

Is there or could there be a way to improve a bit the DevXP by providing ways to create distribution in one directory with the resources like

@orangy ndex.html

, the

.wasm

file (and the

.wat

one when it will be restored) and the

.js

file and optionnaly run a web server without having to run a browser (broken on my Linux installation due to some assumption on the executable name + not super practical since a flag is usually needed)? Currently I do that with a script not sure if there is a better way. Also how are we supposed to deploy website without that?

How does K/WASM plan to support memory64 proposal, specifically current unsafe wasi interop apis, where pointer is UInt? Will it be similar to K/N with 2 different targets, or no?

Is Console available from Kotlin/Wasm?

Unless I am mistaken, KT-22635 looks like fixed with Kotlin/JS but not Kotlin/Wasm. Is it expected? This is fine with Kotlin/JS (thanks for fixing that BTW):

fun main() {
	window.onload = { document.body?.sayHello() }
}

With Kotlin/Wasm, I need to write:

fun main() {
    window.onload = {
        document.body?.sayHello()
        null
    }
}

To make it compile.