That's a good point, thanks. My understanding is that work exposes nearly the full tree-sitter runtime API, but relies on tree-sitter's standard tech for conve

That's a good point, thanks. My understanding is that work exposes nearly the full tree-sitter runtime API, but relies on tree-sitter's standard tech for converting javascript grammar specifications to separately compiled C code. This work instead exposes a minimal subset of tree-sitter functionality, but enables defining parsers entirely in Swift -- eliminating the need for javascript and mixed-language targets, and streamlining the build process.