mattvioli
commented
1 month ago Looks like tsserver was renamed to ts_ls
Have you tried nenaming it in your config?
Closed laycookie closed 2 weeks ago
mattvioli
commented
1 month ago Looks like tsserver was renamed to ts_ls
Have you tried nenaming it in your config?
laycookie
commented
1 month ago Looks like
tsserverwas renamed tots_lsHave you tried nenaming it in your config?
I have tried it but I get [mason-lspconfig.nvim] Server "ts_ls" is not a valid entery in ensure_installed. Make sure to only provide lspconfig server names.
mattvioli
commented
1 month ago Ah you might need to update mason-lspconfig as well.
I got this error today, and just used lazy.nvim to auto update my plugins and it went away.
laycookie
commented
1 month ago @mattvioli Thanks, I thought it automatically updates when you clear the data from .local but apparently it doesn't. The name did switch from TSserver to ts_ls however the the LSP still doesn't work for some reason.
lukepafford
commented
3 weeks ago Idk who is ultimately to blame for this, but I'm commenting my disgust here nonetheless.
I've tried like 18 different times in the past few weeks to get the freaking Typescript LSP to work on my previous working configs that is deployed to both a Mac and a Linux machine. Don't give me this crap about "WHAT ARE YOU STUPID, JUST RENAME TSSERVER TO TS_LS HAR HAR HAR"
Admittedly, I didn't deep dive the living crap out of it because it's always a nuisance to dedicate time to a configuration that breaks.
Nahhh aint no way I really had to configure this working hack.
noahbald
commented
3 weeks ago Seems to be introduced by this commit
If you're using lazy, you can restore to this commit in your lazy-lock.json
"nvim-lspconfig": { "branch": "master", "commit": "36f21ab9555d" },The issue for me doesn't seem to be tsserver, but that nvim-lspconfig renamed the configs directory from server_configurations to configs
laycookie
commented
2 weeks ago Seems to be introduced by this commit
If you're using lazy, you can restore to this commit in your
lazy-lock.json"nvim-lspconfig": { "branch": "master", "commit": "36f21ab9555d" },The issue for me doesn't seem to be tsserver, but that nvim-lspconfig renamed the configs directory from
server_configurationstoconfigs
Thanks for the reply, finnily got around to testing it but sadly the problem is still there. Notably I switched to denols. I also noticed that apparently the issue is there with all of my none rust LSPs. (I have a good guess to why rust works, but for the sake of making it simple just assume no LSP are being enabled.)
laycookie
commented
2 weeks ago Mystery solved I forgot to init everything.
require('mason-lspconfig').setup({
handlers = {
function(server_name)
require('lspconfig')[server_name].setup({})
end,
},
})
Problem description
tsserver is not loading in
Why do you think this is an issue with mason-lspconfig.nvim?
I'm attempting to install, and use,
tsservertrough mason-lspconfig so I assume it is fault of mason-lspconfig for not starting up the Lsp.Neovim version (>= 0.7)
nvim --version NVIM v0.10.1 Build type: Release LuaJIT 2.1.1693350652 Run "nvim -V1 -v" for more info
Operating system/version
Linux nixos 6.6.47 #1-NixOS SMP PREEMPT_DYNAMIC Mon Aug 19 04:04:32 UTC 2024 x86_64 GNU/Linux
I've manually reviewed the Nvim LPS client log (
:LspLog) to find potential errorsI've recently downloaded the latest plugin version of mason.nvim, mason-lspconfig.nvim, and nvim-lspconfig
Affected language servers
tsserver
Steps to reproduce
Most of my LSP configuration are stored in the following file. https://github.com/laycookie/dotfiles/blob/main/themes/Dennis/programs/nvim/config/lua/plugins/lspzero.lua
Actual behavior
Tsserver does not appear to be loading in, and does not provide autocomplete.
Expected behavior
I expect autocomplete to appear, and see some more enhanced syntax highlighting compared to the treesitter.
LspInfo
Screenshots or recordings
No response