-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
tsserver has been renamed to ts_ls in nvim-lspconfig #458
Comments
Yup, I just stumbled into this. So I deleted the installed tsserver binary via Mason, and then updated my nvim config to replace
I realise this is because Mason hasn't been updated to reflect the change and so I can't actually install |
if it's of any help until this gets resolved, you can see how i handled the name change in my config here. |
I'm awaiting williamboman/mason-lspconfig.nvim#458 to be resolved.
I cannot change it, MasonUninstall tsserver gives the error "tsserver is not a valid package. What to do? |
run this command in your terminal: config file: |
it works perfectly, thanks :) |
See williamboman/mason-lspconfig.nvim#458 for futher information.
I know the issue is closed, but I'm still a bit confused. I have updated the language server and all references from tsserver to ts_ls. It seems to work, but the deprecation warning is still there. Where is the reference to tsserver that I'm missing if not in my configuration. Or will the warning persist anyway? |
Problem description
Per neovim/nvim-lspconfig#3232,
if you install
tsserver
throughmason-lspconfig
, then you will get a deprecation warning fromnvim-lspconfig
telling you to rename it tots_ls
.Why do you think this is an issue with mason-lspconfig.nvim?
If it's not, then I'm mistaken and I'm sorry
Neovim version (>= 0.7)
11
Operating system/version
Ubuntu
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
snippet:
Actual behavior
Deprecation error
Expected behavior
No deprecation error
LspInfo
LspLog
No response
Healthcheck
Screenshots or recordings
No response
The text was updated successfully, but these errors were encountered: