Closed particledecay closed 1 year ago
Sorry, this is exactly the reason why you should not blindly install all parsers.
@gshpychka
Whether it's all or just this one, I fail to see how that invalidates the issue.
It invalidates this as an nvim-treesitter issue (experimental parsers are marked experimental for a reason; don't install unless you know what you're getting into), as this is nothing we can do anything about.
It's a valid suggestion to make at the wing parser repo, if you care enough about wing.
The Wing team is currently considering extracting the grammar/parser into its own repo, which should fix this. That being said, this is still in the early stages and highly experimental, so don't install unless you need it.
Describe the bug
The specific error I get every time I open neovim:
What I believe is happening here is that I use Nodenv to manage all my system's Node.js versions. However, the version I am currently using is 18.7.0. The development version that wing is using is 18.16.0, and they've added their
.node-version
to version control, thus forcing everyone using Nodenv (or nvm really, since they also have a.nvmrc
file in there) to use explicitly 18.16.0 if any Node process attempts to use that library (such as treesitter).I'm not sure if this is a behavior issue on treesitter's part (I note that the inclusion of wing is experimental), or an issue on wing's part (debatable whether it's a good idea to include
.node-version
in version control).To Reproduce
Expected behavior
Treesitter works and does not generate errors
Output of
:checkhealth nvim-treesitter
Output of
nvim --version
Additional context
No response