tree-sitter

tree-sitter. We assess it under Code in the garden.

Summary

Unlike batch parsers that assume valid input, tree-sitter is designed for interactive use: partial parses stay useful, grammars are maintained per language, and the same core powers syntax highlighting in Neovim, Helix, GitHub, and Zed. You get fast, error-tolerant CSTs suitable for highlighting, structural search, and simple transforms.

When requirements grow into cross-node semantic graphs (data flow, control flow, security models), add tree-sitter-graph on top. For one language and a stable compiler front-end, a native parser or generator like ANTLR may be simpler than adopting the tree-sitter ecosystem.

Details

• Strengths: incremental updates, robust parsing of incomplete code, broad grammar catalog, bindings for Rust/C/Node/Wasm/Python/Go and more.
• Workflow: define or reuse a grammar → generate parser → run queries (pattern match on syntax nodes) in your tool.
• Typical uses: editor syntax highlighting, code outline/folding, lightweight lint rules, test runners that need structure-aware selection.
• Heavier uses: static analysis pipelines, often paired with tree-sitter-graph (CodeQL-style stacks).
• Category: Code / Library, a dependency you link, not a standalone service.
• Pair with: tree-sitter-graph when CST queries are not enough; contrast language-specific compiler APIs when you only target one language.