That's awesome!

btw, the other vscode tree sitter extension also currently uses web-tree-sitter (wasm-based) having switched from the node bindings: https://github.com/EvgeniyPeshkov/syntax-highlighter/commit/02163f5281ce6847fed4f7fbb2fd7d3ed8e21ba5 - it appears one of the reasons to switch was for making the extension cross-platform

Does that answer your question about wether vscode extensions can work with wasm to the affirmative?

i think so

wasm suddenly got a whole lot more interesting for me 🙂

Is wasm the successor to NaCl and Pepper?

perhaps one can see wasm as having inherited characteristics from asm.js and nacl - i don't know much first-hand though :)