I learned from a google search that these days upstream tree-sitter provides WebAssembly bindings. Source: https://github.com/tree-sitter/tree-sitter/tree/mast

I learned from a google search that these days upstream tree-sitter provides WebAssembly bindings. Source: https://github.com/tree-sitter/tree-sitter/tree/master/lib/binding_web https://github.com/tree-sitter/tree-sitter/tree/master/lib/b... NPM: https://www.npmjs.com/package/web-tree-sitter https://www.npmjs.com/package/web-tree-sitter Download from the latest Github release: js file (https://github.com/tree-sitter/tree-sitter/releases/download/v0.22.2/tree-sitter.js https://github.com/tree-sitter/tree-sitter/releases/download...) and wasm file (https://github.com/tree-sitter/tree-sitter/releases/download/v0.22.2/tree-sitter.wasm https://github.com/tree-sitter/tree-sitter/releases/download...) It's great to see upstream maintaining the bindings. I maintain a Typescript/Empscripten/WebAssembtly binding for quickjs and it's more involved than I would like. Besides providing a WASM build, Emscripten can build a lot of C code to straight JS, which you can use in non-WebAssembly browsers, or in runtimes like Cloudflare or Vercel Edge that support WebAssembly but it's a pain in the behind. Unfortunately the tree-sitter upstream doesn't output such a build but given they already maintain the bindings it wouldn't be a lot of effort to pass the option to emcc (set -s WASM=0 -s SINGLE_FILE=1 instead of -s WASM=1)