nvim-treeconfig: upstream nvim-treesitter

### Problem (This is a "work plan" for https://github.com/neovim/neovim/issues/22313 ) https://github.com/nvim-treesitter/nvim-treesitter should be upstreamed in a form similar to [nvim-lspconfig](https://github.com/neovim/nvim-lspconfig), using the power of magic 🌈 Known issues: - queries may be editor specific (nvim vs helix vs ...) - parsers don't always maintain their own queries - supply-chain attacks (malicious parsers) ### Expected behavior Users can easily install the "top 20" treesitter parsers with a single `vim.pack.add{}` call. (Note: Nvim already ships 5 builtin parsers.) - Provide a ~~`neovim/nvim-tsconfig`~~ `neovim/nvim-treeconfig` repo which has a similar role as `neovim/nvim-lspconfig`. - It is "data-only", it doesn't have a "framework". No "indent" support. (Features requiring a framework should live in Nvim's own stdlib.) - Limited scope, only support the "top N" parsers. (Can reconsider this if/when we find a sustainble maintenance model.) - Parser-related shit (including queries) is owned by the parsers. - See sub-issues. ### Reference Other nvim-treesitter alternatives: - https://github.com/lewis6991/ts-install.nvim - https://github.com/arborist-ts/arborist.nvim - https://github.com/romus204/tree-sitter-manager.nvim

Posted by justinmk on Apr 13, 2026, 12:12 PM

Tags

• support (Software)

Related issues

• Add 65536 size support for maps
• TypeScript 7.1 Iteration Plan
• Add the "action" and "method" attributes to <button>
• [FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
• > We were imposed GitHub for so many exercises!
• Add support for Visual Studio 2026 Integration