<@U0BMF6PDJ> I have a question about the new compo...

# webassembly

[crowforkotlin]

@bashor I have a question about the new component-model support added in 2.4.0. Is the plan to eventually bundle wasm-tools directly into Kotlin, and then use wasm-tools to automatically link wasm and wit? Currently I'm already on 2.4.0-build2-11 and manually handling the component-model logic — including linking, build pipeline, and automating the wasm-tools download process.

[Michael Paus]

What makes you think that the component model will be part of 2.4.0? According to https://youtrack.jetbrains.com/projects/KT/issues/KT-64569/Kotlin-Wasm-Support-Component-Model it has been delayed again to 2.5.0-Beta1. I also find this frustrating but that's the way it is.

[crowforkotlin]

Thanks for the clarification! It seems I misunderstood the context of the demo Zalim posted. I’m currently implementing my own Component Model workflow on a 2.4.0 pre-release version, and I want to confirm the official direction: Is the integration of wasm-tools and automatic WIT binding planned for 2.5.0? Or will these still require manual handling by the user for a while longer?

[bashor]

Hey folks,
Re: Component Model support in 2.4.0 and beyond

2.4.0-Beta1 includes small but sufficient changes that allow us to support the Component Model by generating Kotlin bindings with our wit-bindgen fork.
So, basically, with 2.4.0 and our wit-bindgen, everyone can play with the Component Model (including WASI) and build interesting things 😉. Don’t forget to share what you build in this channel!

There are still many moving parts.
In the near term, we will continue improving wit-bindgen: covering more cases, generating better code, fixing bugs, breaking things (maybe), and moving fast. Eventually, we plan to upstream these changes.

One major piece still missing on both the Component Model and our side is the GC ABI. We keep tracking the progress and will be involved in the process.

In the long term, for sure, the goal is to make everything work together smoothly so you can get a component directly from the toolchain and run it in a VM, potentially integrated with the IDE.