Skip to content
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

Closed
dbaeumer opened this issue Mar 4, 2024 · 7 comments
Milestone

Comments

@dbaeumer
Copy link
Member

dbaeumer commented Mar 4, 2024

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.

@lppedd
Copy link

lppedd commented Apr 27, 2024

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.

@dbaeumer
Copy link
Member Author

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

@lppedd
Copy link

lppedd commented Apr 29, 2024

Nice, thanks! We'd like to expose functions to the JS side. Or maybe interoperate with VS Code APIs directly.
Not sure if those options will be covered, but I'll check the blog post once it's out.

@dbaeumer
Copy link
Member Author

Both cases are covered.

@lppedd
Copy link

lppedd commented Apr 29, 2024

Damn, VS Code on 🔥

@dbaeumer dbaeumer added this to the May 2024 milestone May 13, 2024
@dbaeumer
Copy link
Member Author

The blog post is out: https://code.visualstudio.com/blogs/2024/05/08/wasm

@lppedd
Copy link

lppedd commented May 13, 2024

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants