Modules on Producthunt daily

nvim-treesitter

Tue, 27 May 2025 15:30:52 +0800

nvim-treesitter/nvim-treesitter

nvim-treesitter

Treesitter configurations and abstraction layer for Neovim.

[!CAUTION] The master branch is frozen and provided for backward compatibility only. All future updates happen on the main branch, which will become the default branch in the future.

The goal of nvim-treesitter is both to provide a simple and easy way to use the interface for tree-sitter in Neovim and to provide some basic functionality such as highlighting based on it:

Traditional highlighting (left) vs Treesitter-based highlighting (right). More examples can be found in our gallery.

Warning: Treesitter and nvim-treesitter highlighting are an experimental feature of Neovim. Please consider the experience with this plug-in as experimental until Tree-Sitter support in Neovim is stable! We recommend using the nightly builds of Neovim if possible. You can find the current roadmap here. The roadmap and all features of this plugin are open to change, and any suggestion will be highly appreciated!

Nvim-treesitter is based on three interlocking features: language parsers, queries, and modules, where modules provide features – e.g., highlighting – based on queries for syntax objects extracted from a given buffer by language parsers. Users will generally only need to interact with parsers and modules as explained in the next section. For more detailed information on setting these up, see “Advanced setup”.

Quickstart

Requirements

Neovim 0.10 or later (supported up to Neovim 0.12);
tar and curl in your path (or alternatively git);
a C compiler in your path and libstdc++ installed (Windows users please read this!).

Installation

You can install nvim-treesitter with your favorite package manager (or using the native package feature of vim, see :h packages).

NOTE: This plugin is only guaranteed to work with specific versions of language parsers (as specified in the lockfile.json). When upgrading the plugin, you must make sure that all installed parsers are updated to the latest version via :TSUpdate. It is strongly recommended to automate this; e.g., if you are using lazy.nvim, put this in your init.lua file:

1
2
3

require("lazy").setup({
  {"nvim-treesitter/nvim-treesitter", branch = 'master', lazy = false, build = ":TSUpdate"}
})

[!CAUTION]

This plugin does not support lazy-loading.

Make sure to specify the master branch, as the default branch will switch to main in the future.

For other plugin managers such as packer.nvim, see this Installation page from the wiki (Note that this page is community maintained).

Language parsers

Treesitter uses a different parser for every language, which needs to be generated via tree-sitter-cli from a grammar.js file, then compiled to a .so library that needs to be placed in neovim’s runtimepath (typically under parser/{language}.so). To simplify this, nvim-treesitter provides commands to automate this process. If the language is already supported by nvim-treesitter, you can install it with

`1`	`:TSInstall <language_to_install>`

This command supports tab expansion. You can also get a list of all available languages and their installation status with :TSInstallInfo. Parsers not on this list can be added manually by following the steps described under “Adding parsers” below.

To make sure a parser is at the latest compatible version (as specified in nvim-treesitter’s lockfile.json), use :TSUpdate {language}. To update all parsers unconditionally, use :TSUpdate all or just :TSUpdate.

Modules

Each module provides a distinct tree-sitter-based feature such as highlighting, indentation, or folding; see :h nvim-treesitter-modules or “Available modules” below for a list of modules and their options.

Following examples assume that you are configuring neovim with lua. If you are using vimscript, see :h lua-heredoc. All modules are disabled by default and need to be activated explicitly in your init.lua, e.g., via

require'nvim-treesitter.configs'.setup {
  -- A list of parser names, or "all" (the listed parsers MUST always be installed)
  ensure_installed = { "c", "lua", "vim", "vimdoc", "query", "markdown", "markdown_inline" },

  -- Install parsers synchronously (only applied to `ensure_installed`)
  sync_install = false,

  -- Automatically install missing parsers when entering buffer
  -- Recommendation: set to false if you don't have `tree-sitter` CLI installed locally
  auto_install = true,

  -- List of parsers to ignore installing (or "all")
  ignore_install = { "javascript" },

  ---- If you need to change the installation directory of the parsers (see -> Advanced Setup)
  -- parser_install_dir = "/some/path/to/store/parsers", -- Remember to run vim.opt.runtimepath:append("/some/path/to/store/parsers")!

  highlight = {
    enable = true,

    -- NOTE: these are the names of the parsers and not the filetype. (for example if you want to
    -- disable highlighting for the `tex` filetype, you need to include `latex` in this list as this is
    -- the name of the parser)
    -- list of language that will be disabled
    disable = { "c", "rust" },
    -- Or use a function for more flexibility, e.g. to disable slow treesitter highlight for large files
    disable = function(lang, buf)
        local max_filesize = 100 * 1024 -- 100 KB
        local ok, stats = pcall(vim.loop.fs_stat, vim.api.nvim_buf_get_name(buf))
        if ok and stats and stats.size > max_filesize then
            return true
        end
    end,

    -- Setting this to true will run `:h syntax` and tree-sitter at the same time.
    -- Set this to `true` if you depend on 'syntax' being enabled (like for indentation).
    -- Using this option may slow down your editor, and you may see some duplicate highlights.
    -- Instead of true it can also be a list of languages
    additional_vim_regex_highlighting = false,
  },
}

Each module can also be enabled or disabled interactively through the following commands:

:TSBufEnable {module} " enable module on current buffer
:TSBufDisable {module} " disable module on current buffer
:TSEnable {module} [{ft}] " enable module on every buffer. If filetype is specified, enable only for this filetype.
:TSDisable {module} [{ft}] " disable module on every buffer. If filetype is specified, disable only for this filetype.
:TSModuleInfo [{module}] " list information about modules state for each filetype

Check :h nvim-treesitter-commands for a list of all available commands. It may be necessary to reload the buffer (e.g., via :e) after enabling a module interactively.

Supported languages

For nvim-treesitter to support a specific feature for a specific language requires both a parser for that language and an appropriate language-specific query file for that feature.

The following is a list of languages for which a parser can be installed through :TSInstall; a checked box means that nvim-treesitter also contains queries at least for the highlight module.

Experimental parsers are parsers that have a maintainer but are not stable enough for daily use yet.

We are looking for maintainers to add more parsers and to write query files for their languages. Check our tracking issue for open language requests.

ada (maintained by @briot)
agda (maintained by @Decodetalkers)
angular (experimental, maintained by @dlvandenberg)
apex (maintained by @aheber, @xixiaofinland)
arduino (maintained by @ObserverOfTime)
asm (maintained by @RubixDev)
astro (maintained by @virchau13)
authzed (maintained by @mattpolzin)
awk
bash (maintained by @TravonteD)
bass (maintained by @amaanq)
beancount (maintained by @polarmutex)
bibtex (maintained by @theHamsta, @clason)
bicep (maintained by @amaanq)
bitbake (maintained by @amaanq)
blade (maintained by @calebdw)
blueprint (experimental, maintained by @gabmus)
bp (maintained by @ambroisie)
brightscript (maintained by @ajdelcimmuto)
c (maintained by @amaanq)
c_sharp (maintained by @amaanq)
caddy (maintained by @opa-oz)
cairo (maintained by @amaanq)
capnp (maintained by @amaanq)
chatito (maintained by @ObserverOfTime)
circom (maintained by @alexandr-martirosyan)
clojure (maintained by @NoahTheDuke)
cmake (maintained by @uyha)
comment (maintained by @stsewd)
commonlisp (maintained by @theHamsta)
cooklang (maintained by @addcninblue)
corn (maintained by @jakestanger)
cpon (maintained by @amaanq)
cpp (maintained by @theHamsta)
css (maintained by @TravonteD)
csv (maintained by @amaanq)
cuda (maintained by @theHamsta)
cue (maintained by @amaanq)
cylc (maintained by @elliotfontaine)
d (maintained by @amaanq)
dart (maintained by @akinsho)
desktop (maintained by @ValdezFOmar)
devicetree (maintained by @jedrzejboczar)
dhall (maintained by @amaanq)
diff (maintained by @gbprod)
disassembly (maintained by @ColinKennedy)
djot (maintained by @NoahTheDuke)
dockerfile (maintained by @camdencheek)
dot (maintained by @rydesun)
doxygen (maintained by @amaanq)
dtd (maintained by @ObserverOfTime)
earthfile (maintained by @glehmann)
ebnf (experimental, maintained by @RubixDev)
editorconfig (maintained by @ValdezFOmar)
eds (maintained by @uyha)
eex (maintained by @connorlay)
elixir (maintained by @connorlay)
elm (maintained by @zweimach)
elsa (maintained by @glapa-grossklag, @amaanq)
elvish (maintained by @elves)
embedded_template
enforce (maintained by @simonvic)
erlang (maintained by @filmor)
facility (maintained by @bryankenote)
faust (maintained by @khiner)
fennel (maintained by @alexmozaidze)
fidl (maintained by @chaopeng)
firrtl (maintained by @amaanq)
fish (maintained by @ram02z)
foam (experimental, maintained by @FoamScience)
forth (maintained by @amaanq)
fortran (maintained by @amaanq)
fsh (maintained by @mgramigna)
fsharp (maintained by @nsidorenco)
func (maintained by @amaanq)
fusion (maintained by @jirgn)
GAP system (maintained by @reiniscirpons)
GAP system test files (maintained by @reiniscirpons)
Godot (gdscript) (maintained by @PrestonKnopp)
gdshader (maintained by @godofavacyn)
git_config (maintained by @amaanq)
git_rebase (maintained by @gbprod)
gitattributes (maintained by @ObserverOfTime)
gitcommit (maintained by @gbprod)
gitignore (maintained by @theHamsta)
gleam (maintained by @amaanq)
Glimmer and Ember (maintained by @NullVoxPopuli)
glimmer_javascript (maintained by @NullVoxPopuli)
glimmer_typescript (maintained by @NullVoxPopuli)
glsl (maintained by @theHamsta)
GN (Generate Ninja) (maintained by @amaanq)
gnuplot (maintained by @dpezto)
go (maintained by @theHamsta, @WinWisely268)
goctl (maintained by @chaozwn)
Godot Resources (gdresource) (maintained by @pierpo)
gomod (maintained by @camdencheek)
gosum (maintained by @amaanq)
gotmpl (maintained by @qvalentin)
gowork (maintained by @omertuc)
gpg (maintained by @ObserverOfTime)
graphql (maintained by @bkegley)
gren (maintained by @MaeBrooks)
groovy (maintained by @murtaza64)
gstlaunch (maintained by @theHamsta)
hack
hare (maintained by @amaanq)
haskell (maintained by @mrcjkb)
haskell_persistent (maintained by @lykahb)
hcl (maintained by @MichaHoffmann)
heex (maintained by @connorlay)
helm (maintained by @qvalentin)
hjson (maintained by @winston0410)
hlsl (maintained by @theHamsta)
hlsplaylist (maintained by @Freed-Wu)
hocon (maintained by @antosha417)
hoon (experimental, maintained by @urbit-pilled)
html (maintained by @TravonteD)
htmldjango (experimental, maintained by @ObserverOfTime)
http (maintained by @amaanq, @NTBBloodbath)
hurl (maintained by @pfeiferj)
hyprlang (maintained by @luckasRanarison)
idl (maintained by @cathaysia)
idris (maintained by @srghma)
ini (experimental, maintained by @theHamsta)
inko (maintained by @yorickpeterse)
ipkg (maintained by @srghma)
ispc (maintained by @fab4100)
janet_simple (maintained by @sogaiu)
java (maintained by @p00f)
javadoc (maintained by @rmuir)
javascript (maintained by @steelsojka)
jinja (maintained by @cathaysia)
jinja_inline (maintained by @cathaysia)
jq (maintained by @ObserverOfTime)
jsdoc (maintained by @steelsojka)
json (maintained by @steelsojka)
json5 (maintained by @Joakker)
JSON with comments (maintained by @WhyNotHugo)
jsonnet (maintained by @nawordar)
julia (maintained by @fredrikekre)
just (maintained by @Hubro)
kcl (maintained by @bertbaron)
kconfig (maintained by @amaanq)
kdl (maintained by @amaanq)
kotlin (maintained by @SalBakraa)
koto (maintained by @irh)
kusto (maintained by @Willem-J-an)
lalrpop (maintained by @traxys)
latex (maintained by @theHamsta, @clason)
ledger (maintained by @cbarrete)
leo (maintained by @r001)
linkerscript (maintained by @amaanq)
liquid (maintained by @hankthetank27)
liquidsoap (maintained by @toots)
llvm (maintained by @benwilliamgraham)
lua (maintained by @muniftanjim)
luadoc (maintained by @amaanq)
lua patterns (maintained by @amaanq)
luau (maintained by @amaanq)
m68k (maintained by @grahambates)
make (maintained by @lewis6991)
markdown (basic highlighting) (experimental, maintained by @MDeiml)
markdown_inline (needed for full highlighting) (experimental, maintained by @MDeiml)
matlab (maintained by @acristoffers)
menhir (maintained by @Kerl13)
mermaid (experimental)
meson (maintained by @Decodetalkers)
mlir (experimental, maintained by @artagnon)
muttrc (maintained by @Freed-Wu)
nasm (maintained by @ObserverOfTime)
nginx (maintained by @opa-oz)
nickel
nim (maintained by @aMOPel)
nim_format_string (maintained by @aMOPel)
ninja (maintained by @alemuller)
nix (maintained by @leo60228)
norg (maintained by @JoeyGrajciar, @vhyrro)
nqc (maintained by @amaanq)
nu (maintained by @abhisheksingh0x558)
objc (maintained by @amaanq)
objdump (maintained by @ColinKennedy)
ocaml (maintained by @undu)
ocaml_interface (maintained by @undu)
ocamllex (maintained by @undu)
odin (maintained by @amaanq)
pascal (maintained by @Isopod)
passwd (maintained by @amaanq)
pem (maintained by @ObserverOfTime)
perl (maintained by @RabbiVeesh, @LeoNerd)
php (maintained by @tk-shirasaka, @calebdw)
php_only (maintained by @tk-shirasaka, @calebdw)
phpdoc (experimental, maintained by @mikehaertl)
pioasm (maintained by @leo60228)
po (maintained by @amaanq)
pod (maintained by @RabbiVeesh, @LeoNerd)
Path of Exile item filter (experimental, maintained by @ObserverOfTime)
pony (maintained by @amaanq, @mfelsche)
powershell (maintained by @L2jLiga)
printf (maintained by @ObserverOfTime)
prisma (maintained by @elianiva)
problog (maintained by @foxyseta)
prolog (maintained by @foxyseta)
promql (maintained by @MichaHoffmann)
properties (maintained by @ObserverOfTime)
proto (maintained by @treywood)
prql (maintained by @matthias-Q)
psv (maintained by @amaanq)
pug (experimental, maintained by @zealot128)
puppet (maintained by @amaanq)
purescript (maintained by @postsolar)
PyPA manifest (maintained by @ObserverOfTime)
python (maintained by @stsewd, @theHamsta)
ql (maintained by @pwntester)
qmldir (maintained by @amaanq)
qmljs (maintained by @Decodetalkers)
Tree-Sitter query language (maintained by @steelsojka)
r (maintained by @ribru17)
racket
ralph (maintained by @tdroxler)
rasi (maintained by @Fymyte)
razor (maintained by @tris203)
rbs (maintained by @joker1007)
re2c (maintained by @amaanq)
readline (maintained by @ribru17)
regex (maintained by @theHamsta)
rego (maintained by @FallenAngel97)
pip requirements (maintained by @ObserverOfTime)
rescript (maintained by @ribru17)
rnoweb (maintained by @bamonroe)
robot (maintained by @Hubro)
robots (maintained by @opa-oz)
roc (maintained by @nat-418)
ron (maintained by @amaanq)
rst (maintained by @stsewd)
ruby (maintained by @TravonteD)
runescript (maintained by @2004Scape)
rust (maintained by @amaanq)
scala (maintained by @stevanmilic)
scfg (maintained by @WhyNotHugo)
scheme
scss (maintained by @elianiva)
sflog (maintained by @aheber, @xixiaofinland)
slang (experimental, maintained by @theHamsta)
slim (maintained by @theoo)
slint (maintained by @hunger)
smali (maintained by @amaanq)
smithy (maintained by @amaanq, @keynmol)
snakemake (experimental)
solidity (maintained by @amaanq)
soql (maintained by @aheber, @xixiaofinland)
sosl (maintained by @aheber, @xixiaofinland)
sourcepawn (maintained by @Sarrus1)
sparql (maintained by @GordianDziwis)
sql (maintained by @derekstride)
squirrel (maintained by @amaanq)
ssh_config (maintained by @ObserverOfTime)
starlark (maintained by @amaanq)
strace (maintained by @amaanq)
styled (maintained by @mskelton)
supercollider (maintained by @madskjeldgaard)
superhtml (maintained by @rockorager)
surface (maintained by @connorlay)
svelte (maintained by @amaanq)
sway (maintained by @ribru17)
swift (maintained by @alex-pinkus)
sxhkdrc (maintained by @RaafatTurki)
systemtap (maintained by @ok-ryoko)
t32 (maintained by @xasc)
tablegen (maintained by @amaanq)
tact (maintained by @novusnota)
tcl (maintained by @lewis6991)
teal (maintained by @euclidianAce)
templ (maintained by @vrischmann)
tera (maintained by @uncenter)
terraform (maintained by @MichaHoffmann)
textproto (maintained by @Porter)
thrift (maintained by @amaanq, @duskmoon314)
tiger (maintained by @ambroisie)
tlaplus (maintained by @ahelwer, @susliko)
tmux (maintained by @Freed-Wu)
todotxt (experimental, maintained by @arnarg)
toml (maintained by @tk-shirasaka)
tsv (maintained by @amaanq)
tsx (maintained by @steelsojka)
turtle (maintained by @GordianDziwis)
twig (maintained by @gbprod)
typescript (maintained by @steelsojka)
typespec (maintained by @happenslol)
typoscript (maintained by @Teddytrombone)
typst (maintained by @uben0, @RaafatTurki)
udev (maintained by @ObserverOfTime)
ungrammar (maintained by @Philipp-M, @amaanq)
unison (maintained by @tapegram)
usd (maintained by @ColinKennedy)
uxn tal (maintained by @amaanq)
v (maintained by @kkharji, @amaanq)
vala (maintained by @Prince781)
vento (maintained by @wrapperup, @oscarotero)
verilog (maintained by @zhangwwpeng)
vhdl (maintained by @jpt13653903)
vhs (maintained by @caarlos0)
vim (maintained by @clason)
vimdoc (maintained by @clason)
vrl (maintained by @belltoy)
vue (maintained by @WhyNotHugo, @lucario387)
wgsl (maintained by @szebniok)
wgsl_bevy (maintained by @theHamsta)
wing (maintained by @gshpychka, @MarkMcCulloh)
wit (maintained by @liamwh)
xcompose (maintained by @ObserverOfTime)
xml (maintained by @ObserverOfTime)
xresources (maintained by @ValdezFOmar)
yaml (maintained by @amaanq)
yang (maintained by @Hubro)
yuck (maintained by @Philipp-M, @amaanq)
zathurarc (maintained by @Freed-Wu)
zig (maintained by @amaanq)
ziggy (maintained by @rockorager)
ziggy_schema (maintained by @rockorager)

For related information on the supported languages, including related plugins, see this wiki page.

Available modules

Modules provide the top-level features of nvim-treesitter. The following is a list of modules included in nvim-treesitter and their configuration via init.lua (where multiple modules can be combined in a single call to setup). Note that not all modules work for all languages (depending on the queries available for them). Additional modules can be provided as external plugins.

Highlight

Consistent syntax highlighting.

require'nvim-treesitter.configs'.setup {
  highlight = {
    enable = true,
    -- Setting this to true will run `:h syntax` and tree-sitter at the same time.
    -- Set this to `true` if you depend on 'syntax' being enabled (like for indentation).
    -- Using this option may slow down your editor, and you may see some duplicate highlights.
    -- Instead of true it can also be a list of languages
    additional_vim_regex_highlighting = false,
  },
}

To customize the syntax highlighting of a capture, simply define or link a highlight group of the same name:

1
2

-- Highlight the @foo.bar capture group with the "Identifier" highlight group
vim.api.nvim_set_hl(0, "@foo.bar", { link = "Identifier" })

For a language-specific highlight, append the name of the language:

1
2

-- Highlight @foo.bar as "Identifier" only in Lua files
vim.api.nvim_set_hl(0, "@foo.bar.lua", { link = "Identifier" })

See :h treesitter-highlight-groups for details.

Incremental selection

Incremental selection based on the named nodes from the grammar.

require'nvim-treesitter.configs'.setup {
  incremental_selection = {
    enable = true,
    keymaps = {
      init_selection = "gnn", -- set to `false` to disable one of the mappings
      node_incremental = "grn",
      scope_incremental = "grc",
      node_decremental = "grm",
    },
  },
}

Indentation

Indentation based on treesitter for the = operator. NOTE: This is an experimental feature.

require'nvim-treesitter.configs'.setup {
  indent = {
    enable = true
  }
}

Folding

Tree-sitter based folding (implemented in Neovim itself, see :h vim.treesitter.foldexpr()). To enable it for the current window, set

1
2

vim.wo.foldmethod = 'expr'
vim.wo.foldexpr = 'v:lua.vim.treesitter.foldexpr()'

This will respect your foldminlines and foldnestmax settings.

Advanced setup

Changing the parser install directory

If you want to install the parsers to a custom directory you can specify this directory with parser_install_dir option in that is passed to setup. nvim-treesitter will then install the parser files into this directory.

This directory must be writeable and must be explicitly prepended to the runtimepath. For example:

  -- It MUST be at the beginning of runtimepath. Otherwise the parsers from Neovim itself
  -- is loaded that may not be compatible with the queries from the 'nvim-treesitter' plugin.
  vim.opt.runtimepath:prepend("/some/path/to/store/parsers")

  require'nvim-treesitter.configs'.setup {
    parser_install_dir = "/some/path/to/store/parsers",

    ...

  }

If this option is not included in the setup options, or is explicitly set to nil then the default install directories will be used. If this value is set the default directories will be ignored.

Bear in mind that any parser installed into a parser folder on the runtime path will still be considered installed. (For example if “~/.local/share/nvim/site/parser/c.so” exists then the “c” parser will be considered installed, even though it is not in parser_install_dir)

The default paths are:

first the package folder. Where nvim-treesitter is installed.
second the site directory. This is the “site” subdirectory of stdpath("data").

Adding parsers

If you have a parser that is not on the list of supported languages (either as a repository on Github or in a local directory), you can add it manually for use by nvim-treesitter as follows:

Clone the repository or create a new project in, say, ~/projects/tree-sitter-zimbu. Make sure that the tree-sitter-cli executable is installed and in your path; see https://tree-sitter.github.io/tree-sitter/creating-parsers#installation for installation instructions.
Run tree-sitter generate in this directory (followed by tree-sitter test for good measure).
Add the following snippet to your init.lua:

local parser_config = require "nvim-treesitter.parsers".get_parser_configs()
parser_config.zimbu = {
  install_info = {
    url = "~/projects/tree-sitter-zimbu", -- local path or git repo
    files = {"src/parser.c"}, -- note that some parsers also require src/scanner.c or src/scanner.cc
    -- optional entries:
    branch = "main", -- default branch in case of git repo if different from master
    generate_requires_npm = false, -- if stand-alone parser without npm dependencies
    requires_generate_from_grammar = false, -- if folder contains pre-generated src/parser.c
  },
  filetype = "zu", -- if filetype does not match the parser name
}

If you wish to set a specific parser for a filetype, you should use vim.treesitter.language.register():

`1`	`vim.treesitter.language.register('python', 'someft') -- the someft filetype will use the python parser and queries.`

Note this requires Nvim v0.9.

Start nvim and :TSInstall zimbu.

You can also skip step 2 and use :TSInstallFromGrammar zimbu to install directly from a grammar.js in the top-level directory specified by url. Once the parser is installed, you can update it (from the latest revision of the main branch if url is a Github repository) with :TSUpdate zimbu.

Note that neither :TSInstall nor :TSInstallFromGrammar copy query files from the grammar repository. If you want your installed grammar to be useful, you must manually add query files to your local nvim-treesitter installation. Note also that module functionality is only triggered if your language’s filetype is correctly identified. If Neovim does not detect your language’s filetype by default, you can use Neovim’s vim.filetype.add() to add a custom detection rule.

If you use a git repository for your parser and want to use a specific version, you can set the revision key in the install_info table for you parser config.

Adding queries

Queries are what nvim-treesitter uses to extract information from the syntax tree; they are located in the queries/{language}/* runtime directories (see :h rtp), like the queries folder of this plugin, e.g. queries/{language}/{locals,highlights,textobjects}.scm. Other modules may require additional queries such as folding.scm. You can find a list of all supported capture names in CONTRIBUTING.md.

The first query file on runtimepath will be used (see :h treesitter-query). If you want to make a query on the user config extend other queries instead of replacing them, see :h treesitter-query-modeline-extends.

If you want to completely override a query, you can use :h vim.treesitter.query.set(). For example, to override the injections queries from c with your own:

`1`	`vim.treesitter.query.set("c", "injections", "(comment) @comment")`

Note: when using query.set(), all queries in the runtime directories will be ignored.

Adding modules

If you wish you write your own module, you need to support

tree-sitter language detection support;
attaching and detaching to buffers;
all nvim-treesitter commands.

At the top level, you can use the define_modules function to define one or more modules or module groups:

require'nvim-treesitter'.define_modules {
  my_cool_plugin = {
    attach = function(bufnr, lang)
      -- Do cool stuff here
    end,
    detach = function(bufnr)
      -- Undo cool stuff here
    end,
    is_supported = function(lang)
      -- Check if the language is supported
    end
  }
}

with the following properties:

module_path specifies a require path (string) that exports a module with an attach and detach function. This is not required if the functions are on this definition.
enable determines if the module is enabled by default. This is usually overridden by the user.
disable takes a list of languages that this module is disabled for. This is usually overridden by the user.
is_supported takes a function that takes a language and determines if this module supports that language.
attach takes a function that attaches to a buffer. This is required if module_path is not provided.
detach takes a function that detaches from a buffer. This is required if module_path is not provided.

Extra features

Statusline indicator

1
2

echo nvim_treesitter#statusline(90)  " 90 can be any length
module->expression_statement->call->identifier

Utilities

You can get some utility functions with

`1`	`local ts_utils = require 'nvim-treesitter.ts_utils'`

Check :h nvim-treesitter-utils for more information.

Troubleshooting

Before doing anything, make sure you have the latest version of this plugin and run :checkhealth nvim-treesitter. It can also help to update the parsers via :TSUpdate.

Feature `X` does not work for `{language}`…

First, check the health#nvim_treesitter#check and the health#treesitter#check sections of :checkhealth for any warning. If there is one, it’s highly likely that this is the cause of the problem.

Next check the ## Parser/Features subsection of the health#nvim_treesitter#check section of :checkhealth to ensure the desired module is enabled for your language. If not, you might be missing query files; see Adding queries.

Finally, ensure Neovim is correctly identifying your language’s filetype using the :echo &filetype command while one of your language’s files is open in Neovim. If not, add a short Vimscript file to nvim-treesitter’s ftdetect runtime directory following Neovim’s documentation on filetype detection. You can also quickly & temporarily set the filetype for a single buffer with the :set filetype=langname command to test whether it fixes the problem.

If everything is okay, then it might be an actual error. In that case, feel free to open an issue here.

I get `module 'vim.treesitter.query' not found`

Make sure you have the latest version of Neovim.

I get `Error detected while processing .../plugin/nvim-treesitter.vim` every time I open Neovim

This is probably due to a change in a parser’s grammar or its queries. Try updating the parser that you suspect has changed (:TSUpdate {language}) or all of them (:TSUpdate). If the error persists after updating all parsers, please open an issue.

I get `query error: invalid node type at position`

This could be due a query file outside this plugin using outdated nodes, or due to an outdated parser.

Make sure you have the parsers up to date with :TSUpdate
Make sure you don’t have more than one parser runtime directory. You can execute this command :echo nvim_get_runtime_file('parser', v:true) to find all runtime directories. If you get more than one path, remove the ones that are outside this plugin (nvim-treesitter directory), so the correct version of the parser is used.

I experience weird highlighting issues similar to #78

This is a well known issue, which arises when the tree and the buffer have gotten out of sync. As this is an upstream issue, we don’t have any definite fix. To get around this, you can force reparsing the buffer with

`1`	`:write \| edit \| TSBufEnable highlight`

This will save, restore and enable highlighting for the current buffer.

I experience bugs when using `nvim-treesitter`’s `foldexpr` similar to #194

This might happen, and is known to happen, with vim-clap. To avoid these kind of errors, please use setlocal instead of set for the respective filetypes.

I run into errors like `module 'nvim-treesitter.configs' not found` at startup

This is because of rtp management in nvim, adding packadd nvim-treesitter should fix the issue.

I want to use Git instead of curl for downloading the parsers

In your Lua config:

`1`	`require("nvim-treesitter.install").prefer_git = true`

I want to use a HTTP proxy for downloading the parsers

You can either configure curl to use additional CLI arguments in your Lua config:

1
2
3

require("nvim-treesitter.install").command_extra_args = {
    curl = { "--proxy", "<proxy url>" },
}

or you can configure git via .gitconfig and use git instead of curl

`1`	`require("nvim-treesitter.install").prefer_git = true`

I want to use a mirror instead of “https://github.com/"

In your Lua config:

for _, config in pairs(require("nvim-treesitter.parsers").get_parser_configs()) do
  config.install_info.url = config.install_info.url:gsub("https://github.com/", "something else")
end

require'nvim-treesitter.configs'.setup {
    --
    --
}

Using an existing parser for another filetype

For example, to use the bash tree-sitter to highlight file with filetype=apkbuild, use:

`1`	`vim.treesitter.language.register("bash", "apkbuild")`

The bash tree-sitter must be installed following the usual procedure as described above.

aws-sdk-java-v2

Sun, 04 May 2025 15:26:09 +0800

aws/aws-sdk-java-v2

AWS SDK for Java 2.0

The AWS SDK for Java 2.0 is a rewrite of 1.0 with some great new features. As with version 1.0, it enables you to easily work with Amazon Web Services but also includes features like non-blocking IO and pluggable HTTP implementation to further customize your applications. You can get started in minutes using Maven or any build system that supports MavenCentral as an artifact source.

Getting Started

Before you begin, you need an AWS account. Please see the Sign Up for AWS section of the developer guide for information about how to create an AWS account and retrieve your AWS credentials.

Minimum requirements

To run the SDK you will need Java 1.8+. For more information about the requirements and optimum settings for the SDK, please see the Installing a Java Development Environment section of the developer guide.

Using the SDK

The recommended way to use the AWS SDK for Java in your project is to consume it from Maven Central.

Importing the BOM

To automatically manage module versions (currently all modules have the same version, but this may not always be the case) we recommend you use the Bill of Materials import as follows:

<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>software.amazon.awssdk</groupId>
      <artifactId>bom</artifactId>
      <version>2.31.35</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  </dependencies>
</dependencyManagement>

Then individual modules may omit the version from their dependency statement:

<dependencies>
  <dependency>
    <groupId>software.amazon.awssdk</groupId>
    <artifactId>ec2</artifactId>
  </dependency>
  <dependency>
    <groupId>software.amazon.awssdk</groupId>
    <artifactId>s3</artifactId>
  </dependency>
  <dependency>
    <groupId>software.amazon.awssdk</groupId>
    <artifactId>dynamodb</artifactId>
  </dependency>
</dependencies>

Individual Services

Alternatively you can add dependencies for the specific services you use only:

<dependency>
  <groupId>software.amazon.awssdk</groupId>
  <artifactId>ec2</artifactId>
  <version>2.31.35</version>
</dependency>
<dependency>
  <groupId>software.amazon.awssdk</groupId>
  <artifactId>s3</artifactId>
  <version>2.31.35</version>
</dependency>

Whole SDK

You can import the whole SDK into your project (includes ALL services). Please note that it is recommended to only import the modules you need.

<dependency>
  <groupId>software.amazon.awssdk</groupId>
  <artifactId>aws-sdk-java</artifactId>
  <version>2.31.35</version>
</dependency>

See the Set up the AWS SDK for Java section of the developer guide for more usage information.

New Features for 2.0

Provides a way to plug in your own HTTP implementation.
Provides first class support for non-blocking IO in Async clients.

Building From Source

Once you check out the code from GitHub, you can build it using the following commands.

Linux:

./mvnw clean install

# Skip tests, checkstyles, findbugs, etc for quick build
./mvnw clean install -P quick

# Build a specific service module
./mvnw clean install -pl :s3 -P quick --am

Windows:

`1`	`./mvnw.cmd clean install`

Sample Code

You can find sample code for v2 in the following places:

aws-doc-sdk-examples repo.
Integration tests in this repo. They are located in the it directory under each service module, eg: s3-integration-tests

Maintenance and Support for SDK Major Versions

For information about maintenance and support for SDK major versions and their underlying dependencies, see the following in the AWS SDKs and Tools Reference Guide:

Maintenance and Support for Java Versions

We maintain full support on Long-Term Support(LTS) releases: Java 8, Java 11, Java 17, and Java 21. Note that there may be individual features in newer releases that are not supported, because the SDK must be compatible with Java 8.

Giving Feedback

We need your help in making this SDK great. Please participate in the community and contribute to this effort by submitting issues, participating in discussion forums and submitting pull requests through the following channels:

Submit issues - this is the preferred channel to interact with our team
Articulate your feature request or upvote existing ones on our Issues page

Contributors ✨

Thanks goes to these wonderful people (emoji key):

_sullis 💻	_{Austin Brooks} 💻	_{Konrad `ktoso` Malawski} 💻	_{Andrew Hopkins} 💻	_{Adam Thomas} 💻	_{Steven Swor} 💻	_{Carey Burgess} 💻
_{Anuraag Agrawal} 💻	_jeffalder 💻	_Boris 💻	_{Guillaume Corré} 💻	_{Henri Yandell} 💻	_{Ryan Schmitt} 💻	_Somaya 💻
_{Steven Aerts} 💻	_{Steven Wong} 💻	_{Tomasz Elendt} 💻	_{Will Erickson} 💻	_{Julien Hoarau} 💻	_{SEOKHYOENCHOI} 💻	_adriannistor 💻
_{Xian Sun} 💻	_{Andreas Scheja} 💻	_{Anton Egorov} 💻	_roexber 💻	_brharrington 💻	_{Christopher Radek} 💻	_Foivos 💻
_{Frank Wesemann} 💻	_{Gergely Varga} 💻	_Guillermo 💻	_{Henry Heikkinen} 💻	_{Jochen Schalanda} 💻	_{Joe Barnett} 💻	_{Kazuhiro Sera} 💻
_{Krishna Chaithanya Ganta} 💻	_{Lee Packham} 💻	_{Matteo Carrara} 💻	_{Michael Scharp} 💻	_{Miguel Jimenez} 💻	_{Russell Bolles} 💻	_{Russell Scheerer} 💻
_Scott 💻	_{Shin'ya Ueoka} 💻	_sushilamazon 💻	_tomliu4uber 💻	_{Vladimir Orany} 💻	_{Xinyu Hu} 💻	_{Yosef Fertel} 💻
_{Denys Konakhevych} 💻	_{Alex Weibel} 💻	_{Ryan Carper} 💻	_{Jonathan M. Henson} 💻	_{Debora N. Ito} 💻	_{Bret Ambrose} 💻	_{Anna-Karin Salander} 💻
_{John Viegas} 💻	_{Dongie Agnir} 💻	_{Matthew Miller} 💻	_{Benjamin Maizels} 💻	_{Quan Zhou} 💻	_{Zoe Wang} 💻	_{Varun Nandi} 💻
_{Andrew Shore} 💻	_{Kyle Thomson} 💻	_{Sam Fink} 💻	_{Jonathan Bond} 💻	_ajs139 💻	_{Dewey Nguyen} 💻	_{David Leen} 💻
_{Michael Li} 💻	_{Bennett Lynch} 💻	_{Ikko Ashimine} 📖	_{Jamie Liu} 📖	_guillepb10 💻	_{Lorenz Nickel} 📖	_{Erin Yang} 💻
_{Roberto Tyley} 💻	_{Alvin See} 💻	_ron1 💻	_{Sai Kumar Reddy Chandupatla} 💻	_{David Ho} 💻	_{Thomas Turrell-Croft} 💻	_{Steven Shan} 💻
_{Barry O'Neill} 💻	_{Andy Kiesler} 💻	_Martin 💻	_{Paulo Lieuthier} 💻	_{Sébastien Crocquesel} 💻	_{David Negrete} 💻	_{Stephen Flavin} 💻
_{Olivier L Applin} 💻	_{Adrian Chlebosz} 💻	_{Chad Wilson} 💻	_{Manish Dait} 📖	_{Dennis Kieselhorst} 💻	_{Nilesh PS} 💻	_{Steven Swartz} 💻
_{Michael Dimchuk} 💻	_{Nikita Sokolov} 💻	_{Manuel Sugawara} 💻	_Anirudh 💻	_{Hayden Baker} 💻	_{Jaykumar Gosar} 💻	_{Michael Graeb} 💻
_{Michael Grundie} 💻	_{Eckard Mühlich} 💻	_{Tobias Soloschenko} 💻	_{Luis Madrigal} 📖	_{Kirill Chaykin} 💻	_prateek-vats 💻	_Bole1155 💻
_{Thomas Farr} 💻	_{Saranya Somepalli} 💻	_{Ran Vaknin} 💻	_{Greg Oledzki} 💻

This project follows the all-contributors specification. Contributions of any kind welcome!

caddy

Fri, 11 Apr 2025 15:27:14 +0800

caddyserver/caddy

a project

Every site on HTTPS

Caddy is an extensible server platform that uses TLS by default.

Releases · Documentation · Get Help

Powered by

Features

Easy configuration with the Caddyfile
Powerful configuration with its native JSON config
Dynamic configuration with the JSON API
Config adapters if you don’t like JSON
Automatic HTTPS by default
- ZeroSSL and Let’s Encrypt for public names
- Fully-managed local CA for internal names & IPs
- Can coordinate with other Caddy instances in a cluster
- Multi-issuer fallback
- Encrypted ClientHello (ECH) support
Stays up when other servers go down due to TLS/OCSP/certificate-related issues
Production-ready after serving trillions of requests and managing millions of TLS certificates
Scales to hundreds of thousands of sites as proven in production
HTTP/1.1, HTTP/2, and HTTP/3 all supported by default
Highly extensible modular architecture lets Caddy do anything without bloat
Runs anywhere with no external dependencies (not even libc)
Written in Go, a language with higher memory safety guarantees than other servers
Actually fun to use
So much more to discover

Install

The simplest, cross-platform way to get started is to download Caddy from GitHub Releases and place the executable file in your PATH.

See our online documentation for other install instructions.

Build from source

Requirements:

Go 1.24.0 or newer

For development

Note: These steps will not embed proper version information. For that, please follow the instructions in the next section.

1
2
3

$ git clone "https://github.com/caddyserver/caddy.git"
$ cd caddy/cmd/caddy/
$ go build

When you run Caddy, it may try to bind to low ports unless otherwise specified in your config. If your OS requires elevated privileges for this, you will need to give your new binary permission to do so. On Linux, this can be done easily with: sudo setcap cap_net_bind_service=+ep ./caddy

If you prefer to use go run which only creates temporary binaries, you can still do this with the included setcap.sh like so:

`1`	`$ go run -exec ./setcap.sh main.go`

If you don’t want to type your password for setcap, use sudo visudo to edit your sudoers file and allow your user account to run that command without a password, for example:

`1`	`username ALL=(ALL:ALL) NOPASSWD: /usr/sbin/setcap`

replacing username with your actual username. Please be careful and only do this if you know what you are doing! We are only qualified to document how to use Caddy, not Go tooling or your computer, and we are providing these instructions for convenience only; please learn how to use your own computer at your own risk and make any needful adjustments.

With version information and/or plugins

Using our builder tool, xcaddy…

`1`	`$ xcaddy build`

…the following steps are automated:

Create a new folder: mkdir caddy
Change into it: cd caddy
Copy Caddy’s main.go into the empty folder. Add imports for any custom plugins you want to add.
Initialize a Go module: go mod init caddy
(Optional) Pin Caddy version: go get github.com/caddyserver/caddy/v2@version replacing version with a git tag, commit, or branch name.
(Optional) Add plugins by adding their import: _ "import/path/here"
Compile: go build -tags=nobadger,nomysql,nopgx

Quick start

The Caddy website has documentation that includes tutorials, quick-start guides, reference, and more.

We recommend that all users – regardless of experience level – do our Getting Started guide to become familiar with using Caddy.

If you’ve only got a minute, the website has several quick-start tutorials to choose from! However, after finishing a quick-start tutorial, please read more documentation to understand how the software works. 🙂

Overview

Caddy is most often used as an HTTPS server, but it is suitable for any long-running Go program. First and foremost, it is a platform to run Go applications. Caddy “apps” are just Go programs that are implemented as Caddy modules. Two apps – tls and http – ship standard with Caddy.

Caddy apps instantly benefit from automated documentation, graceful on-line config changes via API, and unification with other Caddy apps.

Although JSON is Caddy’s native config language, Caddy can accept input from config adapters which can essentially convert any config format of your choice into JSON: Caddyfile, JSON 5, YAML, TOML, NGINX config, and more.

The primary way to configure Caddy is through its API, but if you prefer config files, the command-line interface supports those too.

Caddy exposes an unprecedented level of control compared to any web server in existence. In Caddy, you are usually setting the actual values of the initialized types in memory that power everything from your HTTP handlers and TLS handshakes to your storage medium. Caddy is also ridiculously extensible, with a powerful plugin system that makes vast improvements over other web servers.

To wield the power of this design, you need to know how the config document is structured. Please see our documentation site for details about Caddy’s config structure.

Nearly all of Caddy’s configuration is contained in a single config document, rather than being scattered across CLI flags and env variables and a configuration file as with other web servers. This makes managing your server config more straightforward and reduces hidden variables/factors.

Full documentation

Our website has complete documentation:

https://caddyserver.com/docs/

The docs are also open source. You can contribute to them here: https://github.com/caddyserver/website

Getting help

We advise companies using Caddy to secure a support contract through Ardan Labs before help is needed.
A sponsorship goes a long way! We can offer private help to sponsors. If Caddy is benefitting your company, please consider a sponsorship. This not only helps fund full-time work to ensure the longevity of the project, it provides your company the resources, support, and discounts you need; along with being a great look for your company to your customers and potential customers!
Individuals can exchange help for free on our community forum at https://caddy.community. Remember that people give help out of their spare time and good will. The best way to get help is to give it first!

Please use our issue tracker only for bug reports and feature requests, i.e. actionable development items (support questions will usually be referred to the forums).

About

Matthew Holt began developing Caddy in 2014 while studying computer science at Brigham Young University. (The name “Caddy” was chosen because this software helps with the tedious, mundane tasks of serving the Web, and is also a single place for multiple things to be organized together.) It soon became the first web server to use HTTPS automatically and by default, and now has hundreds of contributors and has served trillions of HTTPS requests.

The name “Caddy” is trademarked. The name of the software is “Caddy”, not “Caddy Server” or “CaddyServer”. Please call it “Caddy” or, if you wish to clarify, “the Caddy web server”. Caddy is a registered trademark of Stack Holdings GmbH.

Project on X: @caddyserver
Author on X: @mholt6

Caddy is a project of ZeroSSL, a Stack Holdings company.

Debian package repository hosting is graciously provided by Cloudsmith. Cloudsmith is the only fully hosted, cloud-native, universal package management solution, that enables your organization to create, store and share packages in any format, to any place, with total confidence.

Modules on Producthunt daily

nvim-treesitter

nvim-treesitter/nvim-treesitter

nvim-treesitter

Table of contents

Quickstart

Requirements

Installation

Language parsers

Modules

Supported languages

Available modules

Highlight

Incremental selection

Indentation

Folding

Advanced setup

Changing the parser install directory

Adding parsers

Adding queries

Adding modules

Extra features

Statusline indicator

Utilities

Troubleshooting

Feature X does not work for {language}…

I get module 'vim.treesitter.query' not found

I get Error detected while processing .../plugin/nvim-treesitter.vim every time I open Neovim

I get query error: invalid node type at position

I experience weird highlighting issues similar to #78

I experience bugs when using nvim-treesitter’s foldexpr similar to #194

I run into errors like module 'nvim-treesitter.configs' not found at startup

I want to use Git instead of curl for downloading the parsers

I want to use a HTTP proxy for downloading the parsers

I want to use a mirror instead of “https://github.com/"

Using an existing parser for another filetype

aws-sdk-java-v2

aws/aws-sdk-java-v2

AWS SDK for Java 2.0

Getting Started

Sign up for AWS

Minimum requirements

Using the SDK

Importing the BOM

Individual Services

Whole SDK

New Features for 2.0

Building From Source

Sample Code

Maintenance and Support for SDK Major Versions

Maintenance and Support for Java Versions

Giving Feedback

Contributors ✨

caddy

caddyserver/caddy

a project

Every site on HTTPS

Menu

Features

Install

Build from source

For development

With version information and/or plugins

Quick start

Overview

Full documentation

Getting help

About

Feature `X` does not work for `{language}`…

I get `module 'vim.treesitter.query' not found`

I get `Error detected while processing .../plugin/nvim-treesitter.vim` every time I open Neovim

I get `query error: invalid node type at position`

I experience bugs when using `nvim-treesitter`’s `foldexpr` similar to #194

I run into errors like `module 'nvim-treesitter.configs' not found` at startup