Migrate tree-sitter and tree-sitter-ruby to WASM distribution

[wingrunr21]

Move tree-sitter and tree-sitter-ruby to use a WASM build instead of prebuilt binaries. This should yield a better user experience + allow us to drop prebuild.

More info here

[wingrunr21]

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.

[razzeee]

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

[wingrunr21]

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.

[razzeee]

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.

[minkir014]

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.

[wingrunr21]

@razzeee Ya, I think support works in practice but microsoft/vscode#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

[minkir014]

Have you encountered any problems with WASM or it's working properly??

[wingrunr21]

This change is in master. It will go out with the next release.

[minkir014]

When will WASM version of the extension go out??
Maybe, this will help to fix all issues.