Hello! This is my experiment in making nvim-treesitter (which is great and still up-to-date) with a different API: similar to vim.pack. I think it would be awesome for other nvim-treesitter tools (mason, nvim-treesitter itself, and others) to adapt to it so the DX stays coherent.
I’d like you to take a look at it and share your thoughts. I’m not sure if it is worth using at this point, but the experiment went well:
- the API looks and feels complete + similar to
vim.pack - it works on my machine (tm)
Functionality differences:
>It keeps the parser registry, bundled queries, dependency expansion, install flow, indentation engine, and health-reporting ideas, while intentionally leaving out the startup plugin layer, user commands, tiered language UX, and install log UI.
I’ve also moved locks into ts-pack-lock.json, near the vim-pack-lock.json.