2 errors with nvim-treesitter

[sp000n]

I am a new Linux user running Ubuntu 26.04 on wsl2 (Windows 11) and eager to use kickstart.nvim. Despite carefully following the Ubuntu install recipe several times from scratch, I am unable to overcome the following two errors revealed in Nvim by :checkhealth.
Under nvim-treesitter:
X ERROR tree-sitter-cli v0.26.1 is required
/home/ubuntudude/.local/share/nvim/site/
X ERROR is not in runtimepath.

For the sake of brevity, I shan't recount the steps I have taken to try and fix this but, suffice to say, /home/ubuntudude/.local/share/nvim/site/ IS in my .bashrc and does appear in $PATH. Also, tree-sitter is located at /home/ubuntudude/.cargo/bin which is also added to my .bashrc and appers in $PATH.

At this point, I could use a hand. Thanks for having a look.

[BrainArchive]

I had an issue with tree-sitter-cli also not playing well, which caused some errors when I tried to boot up neovim. Not exactly the same situation but this might help.

Installing tree-sitter-cli via apt didn't work for me and I had to install it manually.
So that meant installing a stable version of rust to get cargo, getting cargo-binstall and getting the tree-sitter-cli from there.

curl https://sh.rustup.rs -sSf | sh
curl -L --proto '=https' --tlsv1.2 -sSf https://raw.githubusercontent.com/cargo-bins/cargo-binstall/main/install-from-binstall-release.sh | bash
cargo binstall tree-sitter-cli

[sp000n]

The latter two steps were part of my trouble shooting attempts as per the tree-sitter-cli repo and I've checked them against the commands in my history. They are identical.
The first line which installs Rust's toolchain is new to me so I guess there as already a version installed since I was able to compile tree-sitter. Running it now gave ended with the following which is pretty intimidating:

Rust is installed now. Great!

To get started you may need to restart your current shell.
This would reload your PATH environment variable to include
Cargo's bin directory ($HOME/.cargo/bin).

To configure your current shell, you need to source the
corresponding env file under $HOME/.cargo.

Consider running the right command for your shell (note the leading DOT):
. "$HOME/.cargo/env" # For sh/ash/dash/pdksh/bash
cargo:rerun-if-env-changed=CC_x86_64-unknown-linux-gnu
CC_x86_64-unknown-linux-gnu = None
cargo:rerun-if-env-changed=CC_x86_64_unknown_linux_gnu
CC_x86_64_unknown_linux_gnu = None
cargo:rerun-if-env-changed=HOST_CC
HOST_CC = None
cargo:rerun-if-env-changed=CC
CC = None
cargo:rerun-if-env-changed=CC_ENABLE_DEBUG_OUTPUT
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = None
cargo:rerun-if-env-changed=HOST_CFLAGS
HOST_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS_x86_64_unknown_linux_gnu
CFLAGS_x86_64_unknown_linux_gnu = None
cargo:rerun-if-env-changed=CFLAGS_x86_64-unknown-linux-gnu
CFLAGS_x86_64-unknown-linux-gnu = None`

Thanks for giving it  a try!

[ibamzjr]

Those are two independent lookup paths: the shell PATH selects the Tree-sitter executable, while Neovim's runtimepath selects parsers and queries. Adding ~/.local/share/nvim/site to PATH cannot fix the second warning.

First check the executable Neovim actually resolves:

:lua print(vim.fn.exepath('tree-sitter'))
:lua print(vim.fn.system({ 'tree-sitter', '--version' }))
:lua print(vim.fn.stdpath('data'))

The current nvim-treesitter health check requires CLI 0.26.1 or newer and uses vim.fn.exepath('tree-sitter') (health.lua). Install that version and put Cargo before any older system binary:

cargo install --locked tree-sitter-cli --version 0.26.1 --force
export PATH="$HOME/.cargo/bin:$PATH"
hash -r
tree-sitter --version

Persist the export in the startup file used by WSL (commonly ~/.profile), then fully restart the terminal and Neovim. If :lua print(vim.fn.exepath('tree-sitter')) still shows /usr/bin/tree-sitter, an older package is shadowing Cargo's binary.

For the parser directory, configure nvim-treesitter in Lua; do not add it to the shell PATH:

require('nvim-treesitter').setup {
  install_dir = vim.fn.stdpath('data') .. '/site',
}

Alternatively, if that directory is intentionally managed elsewhere:

vim.opt.runtimepath:prepend(vim.fn.stdpath('data') .. '/site')

Then run :TSUpdate, restart Neovim, and run :checkhealth nvim-treesitter again. The key is that both checks must succeed inside Neovim, not only in the interactive shell.

[sp000n]

This is going to take me a bit to follow. Thank you so much for laying it out and explaining the purpose of each step. I'll report back here.

[sp000n]

So, I only could get as far as the cargo install before failing. Each step you perscribed and the result. I haven't

:lua print(vim.fn.exepath('tree-sitter'))

returned /usr/bin/tree-sitter

:lua print(vim.fn.system({ 'tree-sitter', '--version' }))

returned tree-sitter 0.25.9
** ahah! from your explanation I see my install grabbed an older version for some reason (despite being from the kickstart recipe)

:lua print(vim.fn.stdpath('data'))

returned /home/ubuntudude/.local/share/nvim

cargo install --locked tree-sitter-cli --version 0.26.1 --force

   threw an error
```shell
    Updating crates.io index
error: could not find `tree-sitter-cli` in registry `crates-io` with version `=0.26.1`

Not defeated yet. I have a lead to follow...

[sp000n]

Following a thread from the tree-sitter github, I was able to curl an udpated binary from the repo, copy it into ~/.local/bin/ and that solved the version issue.

Regards the path, I updated and reran nvim with each of the two changes to init.lua but still have not cleared the error in runtimepath.

[sp000n]

This thread appears to have a fix for the runtime path but I cannot find the kickstart version of this nvim-treesitter/health.lua

nvim-treesitter/nvim-treesitter#8606