Allow using globally installed tree-sitter-cli instead of leting source compiled parsers pull tree-sitter-cli again. about nvim-treesitter HOT 8 CLOSED

No details, no repro, nothing we can do.

A global install of treesitter works fine at least for me.

from nvim-treesitter.

I recommend opening an issue with mason (and a lot more details).

from nvim-treesitter.

You can't reproduce this unless you have the same network condition in China. Also this is not a issue with mason. Rather being treesitter's install.js. But here we may have a workaround.

from nvim-treesitter.

I have been there often. While I feel your pain, it's still out of scope for this plugin, especially without any details to make this actionable.

from nvim-treesitter.

Especially since we have a bunch of options already to work around network issues.

from nvim-treesitter.

A simple reproduce just from tree-sitter-fsharp, where the parser is compiled from source.

local parser_config = require "nvim-treesitter.parsers".get_parser_configs()
parser_config.fsharp = {
  install_info = {
    url = "https://github.com/Nsidorenco/tree-sitter-fsharp",
    branch = "develop",
    files = {"src/scanner.cc", "src/parser.c" },
    generate_requires_npm = true,
    requires_generate_from_grammar = true
  },
  filetype = "fsharp",
}

BTW, I have already set the github download link with mirrors, but that can't prevent a script invoked by npm willing download files from github.

from nvim-treesitter.

Nothing we can do about that. That is on the parsers.

Especially if it is not a parser we bundle; we can offer no support for those. (In fact, we would not consider adding this parser for this very reason.)

from nvim-treesitter.

Okay, I'll file an issue at their end.

from nvim-treesitter.