-
Notifications
You must be signed in to change notification settings - Fork 285
Migrate tree-sitter and tree-sitter-ruby to WASM distribution #506
Comments
WASM support was started over the weekend. Just need to test a few things out and verify the solution works cross-platform. VSCode does not officially support WASM in extensions so want to make sure this is functioning as expected. |
Btw just FYI, here's another VSCode addon that has been shipping wasm tree sitter files for some time now https://github.com/georgewfraser/vscode-tree-sitter/tree/master/parsers |
https://github.com/rubyide/vscode-ruby/tree/tree_sitter_wasm 😉 The issue wasn't how to ship. The issue was support. I use the cursor to traverse the tree and a few features in that just landed yesterday. |
|
When do you intend to fully convert prepuilt binaries to WASM to solve problems of prebuilt binaries instead of fixing node-tree-sitter problems since the PR against node-tree-sitter has some problems. |
@razzeee Ya, I think support works in practice but microsoft/vscode#65559. Luckily, the way @minkir014 ASAP |
Have you encountered any problems with WASM or it's working properly?? |
This change is in |
When will WASM version of the extension go out?? |
I doubt it's going to fix all issues but I'm packaging a ton of bug fixes into the next release. I have one final issue to resolve and I will be doing the release. Fix is written just need to test an edge case I thought of today. |
This was shipped in v0.25.0. There was an issue with publishing that version to the Marketplace so v0.25.1 is the first version with the WASM switch. |
Move
tree-sitter
andtree-sitter-ruby
to use a WASM build instead of prebuilt binaries. This should yield a better user experience + allow us to dropprebuild
.More info here
The text was updated successfully, but these errors were encountered: