-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document how to use VS Code's component model tooling to use WASM services inside a VS Code extensions #157
Comments
Hey @dbaeumer! We're interested in running some of our Kotlin code as WASM binaries in VSC. Is this possible ATM? K/WASM requires GC. |
Yes, stay tuned. There will be a blog post soon on how to do that. If the Kotlin code compiles to something that has only a main function (e.g. is more like a OS program) we have already support for it. See https://code.visualstudio.com/blogs/2023/06/05/vscode-wasm-wasi |
Nice, thanks! We'd like to expose functions to the JS side. Or maybe interoperate with VS Code APIs directly. |
Both cases are covered. |
Damn, VS Code on 🔥 |
The blog post is out: https://code.visualstudio.com/blogs/2024/05/08/wasm |
Thanks @dbaeumer. Had a read already and everything makes sense. Had my hopes too high for the "Full extension in Rust" part, but I guess waiting for the WASI spec is better (AFAIU 0.3 targets early/mid 2025). |
With the component model tooling we now have an easy way to integrate WASM services into VS Code extensions. We should document this via samples and a blog post.
The text was updated successfully, but these errors were encountered: