Could not find 'ts_ls' or 'vtsls' lsp client, required by 'vue_ls'.

[SuperMeepBoy]

Hi ! I've been trying for hours to make my configuration work but I always have the error Could not find 'ts_ls' or 'vtsls' lsp client, required by 'vue_ls'..

• Nvim : v0.11.3
• No mason
• Up to date nvim-lspconfig

My config :

local vue_ls_config = {}
vim.lsp.config('vue_ls', vue_ls_config)

local vue_language_server_path = '/usr/lib/node_modules/@vue/language-server'
local vue_plugin = {
    name = '@vue/typescript-plugin',
    location = vue_language_server_path,
    languages = { 'vue' },
    configNamespace = 'typescript',
    enableForWorkspaceTypeScriptVersions = true,
}
vim.lsp.config('vtsls', {
    filetypes = { 'typescript', 'javascript', 'javascriptreact', 'typescriptreact', 'vue' },
    settings = {
        vtsls = {
            tsserver = {
                globalPlugins = {
                    vue_plugin,
                },
            },
        },
    },
})
vim.lsp.enable({'vtsls', 'vue_ls'})

Can anyone help me? Thanks a lot 🙏

[Jak-Ch-ll]

Hi, I ran into the same issue and stumbled upon our question. I think the problem is that both language servers are starting in parallel and if vtsls takes too long vue_ls runs into that issue.

To solve this vue_ls would have to wait for vtsls to be ready. The way I did it is to not enable vue_ls with the other language servers and instead in the on_attach handler of vtsls:

vim.lsp.config('vtsls', {
    filetypes = { ... },
    settings = { ... },
+   on_attach = function()
+       vim.lsp.enable({'vue_ls'})
+   end
})
-vim.lsp.enable({'vtsls', 'vue_ls'})
+vim.lsp.enable({'vtsls'})

I don't love this solution but it seems to work. Maybe someone else has a better solution. And maybe there is even space for 'dependent language servers' in Neovim

[Jak-Ch-ll]

Quick question: is - on_attach: <function @/home/jef/.config/nvim/lua/config/lsp.lua:131> really the right function (so line 131)? Using vim.lsp.config('*', { ... }) later could potentially overwrite it.

[SuperMeepBoy]

Line 131 is the on_attach, after that the vtsls config closes and I have the vim.lsp.enable({'vue_ls'}).

Under that is a vim.api.nvim_create_autocmd I found for bindings (suck as gd,gD, etc.)

[Jak-Ch-ll]

Ok, I'm now officially out of ideas 😅

I would definitely put a print statement into the on_attach just to see if it is getting executed. If it isn't than there must be a reason somewhere. If it is and vim.lsp.enable({ 'vue_ls' }) still does not do anything then there is seriously something weird going on. You can also call vim.lsp.enable({ 'vue_ls' }) directly while Neovim is running and see what happens.

In any case, here is my LspInfo just for you to compare. Maybe you can see something that I've overlooked:

- vtsls:
  - capabilities: {
      textDocument = {
        completion = {
          completionItem = {
            commitCharactersSupport = false,
            deprecatedSupport = true,
            documentationFormat = { "markdown", "plaintext" },
            insertReplaceSupport = true,
            insertTextModeSupport = {
              valueSet = { 1 }
            },
            labelDetailsSupport = true,
            preselectSupport = false,
            resolveSupport = {
              properties = { "documentation", "detail", "additionalTextEdits", "command", "data" }
            },
            snippetSupport = true,
            tagSupport = {
              valueSet = { 1 }
            }
          },
          completionList = {
            itemDefaults = { "commitCharacters", "editRange", "insertTextFormat", "insertTextMode", "data" }
          },
          contextSupport = true,
          insertTextMode = 1
        }
      },
      workspace = {
        fileOperations = {
          didCreate = true,
          didDelete = true,
          didRename = true,
          willCreate = true,
          willDelete = true,
          willRename = true
        }
      }
    }
  - cmd: { "vtsls", "--stdio" }
  - filetypes: typescript, javascript, javascriptreact, typescriptreact, vue
  - on_attach: <function @/home/j/.config/nvim/lua/jak-ch-ll/lsp.lua:148>
  - root_dir: <function @/home/j/.local/share/nvim/lazy/nvim-lspconfig/lsp/vtsls.lua:78>
  - root_markers: tsconfig.json, jsonconfig.json, package.json, .git
  - settings: {
      javascript = {
        updateImportsOnFileMove = "always"
      },
      typescript = {
        updateImportsOnFileMove = "always"
      },
      vtsls = {
        enableMoveToFileCodeAction = true,
        tsserver = {
          globalPlugins = { {
              configNamespace = "typescript",
              enableForWorkspaceTypeScriptVersions = true,
              languages = { "vue" },
              location = "/nix/store/3ha6w4sbv7fqpr7i1xhb15x11gfmvg23-vue-language-server-3.0.4/lib/language-tools/packages/language-server",
              name = "@vue/typescript-plugin"
            } }
        }
      }
    }

[SuperMeepBoy]

Thanks for your time. I printed but nothing is printed (either that or I don't know where I should see it) so there might be an issue with my on_attach function. I will look into it. 🙏

Thanks again for everything!

[Jak-Ch-ll]

Happy to help and good luck 😄

[SuperMeepBoy]

For anyone joining. I tried :

1. :LspStop vue_ls
2. :LspStop vtsls
3. :LspStart vtsls
4. :LspInfo (vtsls is there)
5. :LspStart vue_ls
   -> I still have the error message about vue_ls not finding vtsls or ts_ls lsp client.

[SuperMeepBoy]

Solved. Obviously, I should have read the documentation more closely (which I did but you know… meh).

My vtsls never attached, that's why vue_ls never found it.

I just missed a .jsconfig or .tsconfig at the root of my project to vtsls attached too.

Sorry for wasting your time. Thanks @Jak-Ch-ll for helping out! 😊

[Jak-Ch-ll]

Glad to hear that you found the reason for the issue in the end

Do you need the on_attach stuff or does it work without now, if the first file you open is a Vue file? For me without the on_attach getting the issue around 50% of cases when both servers start in parallel, and I would be interested to know if that's just a me problem 😄

[SuperMeepBoy]

I don't need the on_attach anymore. New challenge is to find how to enable the go to decalaration/implementation. 😂

[Jak-Ch-ll]

Ok good to know and thanks. Then I guess I have to figure out why I'm seemingly the only one with that issue 😅

But I can tell you that the goto stuff just works for me with my usual keybindings. If I goto on a component in the template I'm going there.