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.
VSCode does not officially support WASM in extensions so want to make sure this is functioning as expected.
Just meant to mention that due to that, especially as I'm interested in your findings there. Might have implications for my LS implementation.
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 https://github.com/Microsoft/vscode/issues/65559. Luckily, the way tree-sitter is built the appropriate member functions for memory management can be defined in the types it ships vs those from the WASM spec or emscripten
@minkir014 ASAP
Have you encountered any problems with WASM or it's working properly??
This change is in master. It will go out with the next release.
When will WASM version of the extension go out??
Maybe, this will help to fix all issues.
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.
Most helpful comment
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.