-
-
Notifications
You must be signed in to change notification settings - Fork 275
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
Cannot find package "ts_ls"
#1784
Comments
Here's a temporary work around
|
That does not work for me :C, I get the following warning: [lspconfig] Cannot acces configuration for ls_ts. Ensure this server is listed in |
Getting the same error. After nvim-lspconfig added the deprecation from |
You can find the issue here: williamboman/mason.nvim#1784
another temporary fix could be local lspconfig = require('lspconfig')
require('mason-lspconfig').setup({
ensure_installed = {
'tsserver',
-- others...
},
handlers = {
-- default handler
function(server_name)
lspconfig[server_name].setup({})
end,
tsserver = function()
lspconfig.ts_ls.setup({})
end,
-- other specific handlers...
},
}) hopefully i typed that correctly. |
it looks like ts_ls is now available in the list of available lsps if you run local lspconfig = require('lspconfig')
require('mason-lspconfig').setup({
ensure_installed = {
'ts_ls',
-- others
},
handlers = {
function(server_name)
lspconfig[server_name].setup({})
end
}
}) ts_ls is on the bottom. |
More info: See e.g. williamboman/mason.nvim#1784
I confirm I no longer encounter this error. TypeScript LS working as expected. |
@joshwashywash It worked fine over here! |
I've searched open issues for similar requests
I've manually reviewed logs to find potential errors
I've recently downloaded the latest plugin version of mason.nvim
Problem description
Since neovim/nvim-lspconfig#3232, the correct server name for TypeScript is
ts_ls
instead oftsserver
.Replacing
tsserver
withts_ls
produces the following error:Expected behavior
No error.
Steps to reproduce
Affected packages
No idea.
Neovim version (>= 0.7)
Not willing to disclose
Operating system/version
Not willing to disclose
Healthcheck
Screenshots or recordings
No response
The text was updated successfully, but these errors were encountered: