tree-sitter init
The init command is your starting point for creating a new grammar. When you run it, it sets up a repository with all
the essential files and structure needed for grammar development. Since the command includes git-related files by default,
we recommend using git for version control of your grammar.
tree-sitter init [OPTIONS] # Aliases: i
Generated files
Required files
The following required files are always created if missing:
tree-sitter.json- The main configuration file that determines howtree-sitterinteracts with the grammar. If missing, theinitcommand will prompt the user for the required fields. See below for the full documentation of the structure of this file.package.json- Thenpmmanifest for the parser. This file is required for sometree-sittersubcommands, and if the grammar has dependencies (e.g., another published base grammar that this grammar extends).grammar.js- An empty template for the main grammar file; see the section on creating parsers.
Language bindings
Language bindings are files that allow your parser to be directly used by projects written in the respective language.
The following bindings are created if enabled in tree-sitter.json:
C/C++
Makefile— This file tellsmakehow to compile your language.CMakeLists.txt— This file tellscmakehow to compile your language.bindings/c/tree_sitter/tree-sitter-language.h— This file provides the C interface of your language.bindings/c/tree-sitter-language.pc— This file provides pkg-config metadata about your language's C library.
Go
go.mod— This file is the manifest of the Go module.bindings/go/binding.go— This file wraps your language in a Go module.bindings/go/binding_test.go— This file contains a test for the Go package.
Node
binding.gyp— This file tells Node.js how to compile your language.bindings/node/binding.cc— This file wraps your language in a JavaScript module for Node.js.bindings/node/index.js— This is the file that Node.js initially loads when using your language.bindings/node/index.d.ts— This file provides type hints for your parser when used in TypeScript.bindings/node/binding_test.js— This file contains a test for the Node.js package.
Java
pom.xml- This file is the manifest of the Maven package.bindings/java/main/namespace/language/TreeSitterLanguage.java- This file wraps your language in a Java class.bindings/java/test/TreeSitterLanguageTest.java- This file contains a test for the Java package.
Python
pyproject.toml— This file is the manifest of the Python package.setup.py— This file tells Python how to compile your language.bindings/python/tree_sitter_language/binding.c— This file wraps your language in a Python module.bindings/python/tree_sitter_language/__init__.py— This file tells Python how to load your language.bindings/python/tree_sitter_language/__init__.pyi— This file provides type hints for your parser when used in Python.bindings/python/tree_sitter_language/py.typed— This file provides type hints for your parser when used in Python.bindings/python/tests/test_binding.py— This file contains a test for the Python package.
Rust
Cargo.toml— This file is the manifest of the Rust package.bindings/rust/build.rs— This file tells Rust how to compile your language.bindings/rust/lib.rs— This file wraps your language in a Rust crate when used in Rust.
Swift
Package.swift— This file tells Swift how to compile your language.bindings/swift/TreeSitterLanguage/language.h— This file wraps your language in a Swift module when used in Swift.bindings/swift/TreeSitterLanguageTests/TreeSitterLanguageTests.swift— This file contains a test for the Swift package.
Zig
build.zig- This file tells Zig how to compile your language.build.zig.zon- This file is the manifest of the Zig package.bindings/zig/root.zig- This file wraps your language in a Zig module.bindings/zig/test.zig- This file contains a test for the Zig package.
Additional files
In addition, the following files are created that aim to improve the development experience:
.editorconfig— This file tells your editor how to format your code. More information about this file can be found here..gitattributes— This file tells Git how to handle line endings and tells GitHub which files are generated..gitignore— This file tells Git which files to ignore when committing changes.
Structure of tree-sitter.json
The grammars field
This field is an array of objects, though you typically only need one object in this array unless your repo has
multiple grammars (for example, Typescript and TSX), e.g.,
{
"tree-sitter": [
{
"scope": "source.ruby",
"file-types": [
"rb",
"gemspec",
"Gemfile",
"Rakefile"
],
"first-line-regex": "#!.*\\bruby$"
}
]
}
Basic fields
These keys specify basic information about the parser:
-
scope(required) — A string like"source.js"that identifies the language. We strive to match the scope names used by popular TextMate grammars and by the Linguist library. -
path— A relative path from the directory containingtree-sitter.jsonto another directory containing thesrc/folder, which contains the actual generated parser. The default value is"."(so thatsrc/is in the same folder astree-sitter.json), and this very rarely needs to be overridden. -
external-files— A list of relative paths from the root dir of a parser to files that should be checked for modifications during recompilation. This is useful during development to have changes to other files besides scanner.c be picked up by the cli.
Language detection
These keys help to decide whether the language applies to a given file:
-
file-types— An array of filename suffix strings (not including the dot). The grammar will be used for files whose names end with one of these suffixes. Note that the suffix may match an entire filename. -
first-line-regex— A regex pattern that will be tested against the first line of a file to determine whether this language applies to the file. If present, this regex will be used for any file whose language does not match any grammar'sfile-types. -
content-regex— A regex pattern that will be tested against the contents of the file to break ties in cases where multiple grammars matched the file using the above two criteria. If the regex matches, this grammar will be preferred over another grammar with nocontent-regex. If the regex does not match, a grammar with nocontent-regexwill be preferred over this one. -
injection-regex— A regex pattern that will be tested against a language name to determine whether this language should be used for a potential language injection site. Language injection is described in more detail in the relevant section.
Query paths
These keys specify relative paths from the directory containing tree-sitter.json to the files that control syntax highlighting:
highlights— Path to a highlight query. Default:queries/highlights.scmlocals— Path to a local variable query. Default:queries/locals.scm.injections— Path to an injection query. Default:queries/injections.scm.tags— Path to a tag query. Default:queries/tags.scm.
The metadata field
This field contains information that tree-sitter will use to populate relevant bindings' files, especially their versions.
Typically, this will all be set up when you run tree-sitter init, but you are welcome to update it as you see fit.
version(required) — The current version of your grammar, which should follow semverlicense— The license of your grammar, which should be a valid SPDX licensedescription— The brief description of your grammarauthors(required) — An array of objects that contain anamefield, and optionally anemailandurlfield. Each field is a stringlinks— An object that contains arepositoryfield, and optionally afundingfield. Each field is a stringnamespace— The namespace for theJavaandKotlinbindings, defaults toio.github.tree-sitterif not provided
The bindings field
This field controls what bindings are generated when the init command is run.
Each key is a language name, and the value is a boolean.
c(default:true)go(default:true)java(default:false)node(default:true)python(default:true)rust(default:true)swift(default:false)zig(default:false)
Options
-u/--update
Update outdated generated files, if possible.
Note: Existing files that may have been edited manually are not updated in general. To force an update to such files,
remove them and call tree-sitter init -u again.
-p/--grammar-path <PATH>
The path to the directory containing the grammar.