feat: support volar 1.0

[adalessa]

Volar has updated the options for the language server. see vuejs/language-tools#1916
In order to support this I have update the configuration.
this also has been reported to neovim neovim/neovim#20010 but is more related to the config not the core.

Thanks in advance.

[mikehaertl]

@adalessa With volar 1.0.9 it's missing many capabilities for me now:

method textDocument/definition is not supported by any of the servers registered for the current buffer
method textDocument/hover is not supported by any of the servers registered for the current buffer
method textDocument/codeAction is not supported by any of the servers registered for the current buffer

Do these work for you?

[polyzen]

Those all work for me, tested on https://github.com/archlinux-de/pkgstats.archlinux.de.

[mikehaertl]

@polyzen Thanks. What's your neovim version?

I use the latest nvim-lspconfig and volar versions with neovim 0.8.0.

[polyzen]

0.8.0

[pwang2]

same as @mikehaertl , latest nvim-lspconfig, volar(1.0.9)+neovim 0.8.1. looks like something still wrong.

[polyzen]

For reference I use the following:
https://archlinux.org/packages/community/x86_64/neovim/
https://aur.archlinux.org/packages/vue-language-server

[Lilja]

If you are experiencing issues, have you downloaded both:

• @volar/vue-language-server
• typescript-language-server

If you still are experiencing issues, set the tsdk:

require('lsp-config')['volar'].setup{
  on_attach = on_attach,
  capabilities = capabilities,
  init_options = {
    typescript = {
      tsdk = "/global/npm/install/path/to/node_modules/typescript/lib"
    }
  }
}

[mikehaertl]

@pwang2 See the latest comment here: vuejs/language-tools#1916 (comment)

@mikehaertl It should be resolved by vuejs/language-tools@8daa162

So the issue should hopefully be fixed in the next volar release.

[pwang2]

Thank you @mikehaertl , I also resulted at that comments. :) waiting for 1.0.10.

[mmoya]

For the record, still getting the issue with 1.0.10:

$ nvim --version
NVIM v0.8.1
Build type: Release
LuaJIT 2.1.0-beta3
...

$ .local/share/nvim/mason/packages/vue-language-server/node_modules/.bin/vue-language-server --version
1.0.10

$ git -C .local/share/nvim/site/pack/packer/opt/nvim-lspconfig show --name-only 
commit d346335af862ede0cece75739d789cfdc46c4454 (HEAD -> master, origin/master, origin/HEAD)
...

Solved by setting tsdk = "/usr/lib/node_modules/typescript/lib" (following Lilja's suggestion).

[mikehaertl]

@mmoya Could it be that you're using volar on a project with workspaces? There's a script in https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#volar which required an update, too, to change from serverPath to tdsk.

With that in place 1.0.10 works fine for me.

[mmoya]

@mmoya Could it be that you're using volar on a project with workspaces? There's a script in https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#volar which required an update, too, to change from serverPath to tdsk.

I don't know if I have workspaces or not, which probably means I don't have it. Anyway I solved the issue by setting the tsdk property.