-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
typescriptreact file type does not start lsp automatically #2744
Comments
Same issue for me on:
|
hmm you have a |
please check and fixed the issue |
I had a similar issue using
For me it turned out the problem was the usage of You could potentially quickly validating this by disabling treesitter temporarily. Error message from the neovim logs
Someone was also facing a similar issue with treesitter |
I also have similar issue using {
"neovim/nvim-lspconfig",
event = { "BufReadPre", "BufNewFile" },
dependencies = {
{
"folke/neodev.nvim",
config = function()
require("neodev").setup()
end
},
"williamboman/mason.nvim",
"williamboman/mason-lspconfig.nvim",
{
"j-hui/fidget.nvim",
branch = "legacy"
},
{
"https://git.sr.ht/~whynothugo/lsp_lines.nvim",
config = function()
require("lsp_lines").setup()
end,
},
},
config = function()
require("plugin.config.lsp").setup()
end,
cmd = { "Mason" }
}, |
send a pr |
Description
I have this config for
tsserver
anddenolsp
:LSP starts automatically in any
ts
orjs
filesbut in
tsx
files it does not start automaticallyNeovim version
NVIM v0.10.0-dev-751+gd086bc1e8-Homebrew
Build type: Release
LuaJIT 2.1.0-beta3
Run "nvim -V1 -v" for more info
Nvim-lspconfig version
No response
Operating system and version
macOS 12.6.7
Affected language servers
denols and tsserver
Steps to reproduce
I'm writing a full document here
https://github.com/MiaadTeam/lesvim
Actual behavior
does not start automatically
tsserver
ordenols
ontsx
files.Expected behavior
No response
Minimal config
LSP log
https://gist.github.com/hemedani/0af44169fdeb0c7de850d0b58062bde7#file-lsp-log
The text was updated successfully, but these errors were encountered: