cb58bc593f
Recently I've been pulling a lot of grammars into GitHub's highlighting backend, replacing legacy language support with tree-sitter highlighting queries. Our backend systems have a standard set of highlight captures we expect, very similar to the standard tagging captures we expect. Though end-user applications are free to choose whatever tagging nomenclature they want, I think it's nice to include a checking stage that will help us ensure that we know whether a capture might be recognized or not. It will also help us figure out where we need to expand our standard set of captures (see #1539). |
||
|---|---|---|
| .. | ||
| benches | ||
| config | ||
| loader | ||
| npm | ||
| src | ||
| vendor | ||
| build.rs | ||
| Cargo.toml | ||
| emscripten-version | ||
| README.md | ||
Tree-sitter CLI
The Tree-sitter CLI allows you to develop, test, and use Tree-sitter grammars from the command line. It works on MacOS, Linux, and Windows.
Installation
You can install the tree-sitter-cli with cargo:
cargo install tree-sitter-cli
or with npm:
npm install tree-sitter-cli
You can also download a pre-built binary for your platform from the releases page.
Dependencies
The tree-sitter binary itself has no dependencies, but specific commands have dependencies that must be present at runtime:
- To generate a parser from a grammar, you must have
nodeon your PATH. - To run and test parsers, you must have a C and C++ compiler on your system.
Commands
-
generate- Thetree-sitter generatecommand will generate a Tree-sitter parser based on the grammar in the current working directory. See the documentation for more information. -
test- Thetree-sitter testcommand will run the unit tests for the Tree-sitter parser in the current working directory. See the documentation for more information. -
parse- Thetree-sitter parsecommand will parse a file (or list of files) using Tree-sitter parsers.