| Crates.io | syntastica-parsers-git |
| lib.rs | syntastica-parsers-git |
| version | 0.6.1 |
| created_at | 2023-05-24 19:17:19.225836+00 |
| updated_at | 2025-06-19 16:58:40.643546+00 |
| description | Collection of tree-sitter parsers for syntastica, fetching with git in the build-script |
| homepage | |
| repository | https://github.com/RubixDev/syntastica |
| max_upload_size | |
| id | 873679 |
| size | 88,410 |
syntastica-parsers-gitCollection of tree-sitter parsers for
syntastica, fetching with git in the
build-script.
See the project overview for more information on all parser collections.
Due to the nature of this parser collection, compilation can take a very long time with many parsers enabled, since all parsers are cloned and built every time the build script is run. In a local development environment you can use the following environment variables to reuse files from a previous run.
You can set SYNTASTICA_PARSERS_CLONE_DIR to a directory to clone the parser
repositories to, so that they only have to be built but not downloaded every
time.
Set SYNTASTICA_PARSERS_CACHE_DIR to a directory where all built parsers will
be copied to. When a binary for a parser is already present in that directory,
it will be reused the next time the build script is run.
Some parsers don't include the generated parser.c file in their git checkouts
and instead require users to generate it themselves based on the grammer.js.
This collection supports that, but this requires you to have a working
JavaScript runtime installed on your system. By default, node is assumed, but
you can override that to bun or deno by setting the
SYNTASTICA_PARSERS_JS_RUNTIME environment variable. These parsers will only be
in the all group, so unless you use that group or one of the affected parsers
specifically, you don't have to worry about this.
some featuremost feature