it is sad，i use nvim native lsp

[1096015776]

i know if i write vue3 it is good，can i use it in native lsp，now or in the feture

[soerenmartius]

+1

[ouuan]

I successfully got the diagnostics feature working via https://github.com/neovim/nvim-lspconfig on Arch Linux:

AUR Package: https://aur.archlinux.org/packages/volar-server/

config:

local configs = require'lspconfig/configs'
local util = require 'lspconfig/util'
configs.volar = {
  default_config = {
    cmd = { 'volar-server', '--stdio' },
    filetypes = { 'vue' },
    root_dir = util.root_pattern('package.json', 'vue.config.js'),
    init_options = {
        typescript = {
            serverPath = '/usr/lib/node_modules/typescript/lib/tsserverlibrary.js',
        },
        languageFeatures = {
            references = true,
            definition = true,
            typeDefinition = true,
            callHierarchy = true,
            hover = true,
            rename = true,
            signatureHelp = true,
            codeAction = true,
            completion = {
                defaultTagNameCase = 'both',
                defaultAttrNameCase = 'kebabCase',
                getDocumentNameCasesRequest = true,
                getDocumentSelectionRequest = true,
            },
            documentLink = true,
            codeLens = true,
            diagnostics = true,
        },
        documentFeatures = {
            selectionRange = true,
            foldingRange = true,
            documentSymbol = true,
            documentColor = true,
            documentFormatting = {
                defaultPrintWidth = 100,
                getDocumentPrintWidthRequest = true,
            },
        },
    },
  },
}
lsp.volar.setup{
    on_attach = on_attach,
}

However, when I try to use other features, it shows an error related to neovim/neovim#15469.

[johnsoncodehk]

The problem seems to be that nvim does not support dynamic registration: neovim/neovim#13634

I can try to provide the option to fall back to static registration maybe.

[johnsoncodehk]

Dynamic registration has been unused in 0.27.11, please let me know if it applies.

[yaegassy]

I tried it in my Neovim built-in lsp environment, and it seems to work now. (volar v0.27.11)

volar-nvim-buitin-lsp.mp4

[1096015776]

it is nice ，thanks，could you give me this nvim config，i worried that i am wrong in somewhere

[yaegassy]

@1096015776 Refer to ouuan's settings and adjust the settings to your environment.

[johnsoncodehk]

Please note that opening all features on one language server will cause auto-complete and other features to be blocked by diagnostics. To avoid this problem, you need to divide language features into multiple language servers. (Please refer to the implementation of coc-volar)

[yaegassy]

@1096015776 Does volar now work with nvim lsp? I'm using coc.nvim (coc-volar). nvim lsp is only used for verification purposes, so I've only done a quick check.

If you find my setup is helpful, I'll write it down here.

e.g.:

if filereadable(expand('~/.local/src/volar/node_modules/@volar/server/out/index.js'))

lua << EOF
local configs = require 'lspconfig/configs'
local util = require 'lspconfig/util'

local script_path = os.getenv("HOME") .. "/.local/src/volar/node_modules/@volar/server/out/index.js"
local tslib_path = os.getenv("HOME") .. "/.local/src/volar/node_modules/typescript/lib/tsserverlibrary.js"

configs.volar = {
  default_config = {
    cmd = {"node", script_path, "--stdio"},
    filetypes = {"vue"},
    root_dir = util.root_pattern("package.json", ".git/");
    init_options = {
      typescript = {
        serverPath = tslib_path
      },
      languageFeatures = {
        references =  true,
        definition = true,
        typeDefinition = true,
        callHierarchy = true,
        hover = true,
        rename = true,
        renameFileRefactoring = true,
        signatureHelp = true,
        codeAction = true,
        completion = {
          defaultTagNameCase = 'both',
          defaultAttrNameCase = 'kebabCase',
          getDocumentNameCasesRequest = false,
          getDocumentSelectionRequest = false,
        },
        schemaRequestService = true,
        documentHighlight = true,
        documentLink = true,
        codeLens = { showReferencesNotification = true },
        semanticTokens = true,
        diagnostics = true,
      },
      documentFeatures = {
        selectionRange = false,
        foldingRange = false,
        linkedEditingRange = true,
        documentSymbol = true,
        documentColor = true,
        documentFormatting = {
          defaultPrintWidth = 100,
          getDocumentPrintWidthRequest = true,
        },
      },
    },
    settings = {
      ['volar-api'] = {
        trace = {
          server = "off"
        }
      },
      ['volar-document'] = {
        trace = {
          server = "off"
        }
      },
      ['volar-html'] = {
        trace = {
          server = "off"
        }
      },
      volar = {
        codeLens = {
          references = true,
          pugTools = true,
          scriptSetupTools = true,
        },
        tagNameCase = 'both',
        attrNameCase = 'kebab',
        formatting = {
          printWidth = 100
        },
        autoCompleteRefs = true,
        preferredTagNameCase = 'auto',
        preferredAttrNameCase = 'auto-kebab',
      },
    };
  };
}
EOF

lua require'lspconfig'.volar.setup{}

endif

[johnsoncodehk]

Thanks! And this is some recommend changes:

if filereadable(expand('~/.local/src/volar/node_modules/@volar/server/out/index.js'))

lua << EOF
local configs = require 'lspconfig/configs'
local util = require 'lspconfig/util'

local script_path = os.getenv("HOME") .. "/.local/src/volar/node_modules/@volar/server/out/index.js"
local tslib_path = os.getenv("HOME") .. "/.local/src/volar/node_modules/typescript/lib/tsserverlibrary.js"

configs.volar = {
  default_config = {
    cmd = {"node", script_path, "--stdio"},
    filetypes = {"vue"},
    root_dir = util.root_pattern("package.json", ".git/");
    init_options = {
      typescript = {
        serverPath = tslib_path
      },
      languageFeatures = {
        references =  true,
        definition = true,
        typeDefinition = true,
        callHierarchy = true,
        hover = true,
        rename = true,
        renameFileRefactoring = true,
        signatureHelp = true,
        codeAction = true,
        completion = {
          defaultTagNameCase = 'both',
          defaultAttrNameCase = 'kebabCase',
-          getDocumentNameCasesRequest = false,
-          getDocumentSelectionRequest = false,
        },
        schemaRequestService = true,
        documentHighlight = true,
        documentLink = true,
-        codeLens = { showReferencesNotification = true },
+        codeLens = true,
        semanticTokens = true,
        diagnostics = true,
      },
      documentFeatures = {
-        selectionRange = false,
+        selectionRange = true,
-        foldingRange = false,
+        foldingRange = true,
        linkedEditingRange = true,
        documentSymbol = true,
        documentColor = true,
        documentFormatting = {
          defaultPrintWidth = 100,
-          getDocumentPrintWidthRequest = true,
        },
      },
    },
    settings = {
-      ['volar-api'] = {
-        trace = {
-          server = "off"
-        }
-      },
-      ['volar-document'] = {
-        trace = {
-          server = "off"
-        }
-      },
-      ['volar-html'] = {
-        trace = {
-          server = "off"
-        }
-      },
      volar = {
        codeLens = {
          references = true,
          pugTools = true,
          scriptSetupTools = true,
        },
-        tagNameCase = 'both',
-        attrNameCase = 'kebab',
-        formatting = {
-          printWidth = 100
-        },
-        autoCompleteRefs = true,
-        preferredTagNameCase = 'auto',
-        preferredAttrNameCase = 'auto-kebab',
      },
    };
  };
}
EOF

lua require'lspconfig'.volar.setup{}

endif

[1096015776]

@1096015776 Does volar now work with nvim lsp? I'm using coc.nvim (coc-volar). nvim lsp is only used for verification purposes, so I've only done a quick check.

If you find my setup is helpful, I'll write it down here.

e.g.:

if filereadable(expand('~/.local/src/volar/node_modules/@volar/server/out/index.js'))

lua << EOF
local configs = require 'lspconfig/configs'
local util = require 'lspconfig/util'

local script_path = os.getenv("HOME") .. "/.local/src/volar/node_modules/@volar/server/out/index.js"
local tslib_path = os.getenv("HOME") .. "/.local/src/volar/node_modules/typescript/lib/tsserverlibrary.js"

configs.volar = {
  default_config = {
    cmd = {"node", script_path, "--stdio"},
    filetypes = {"vue"},
    root_dir = util.root_pattern("package.json", ".git/");
    init_options = {
      typescript = {
        serverPath = tslib_path
      },
      languageFeatures = {
        references =  true,
        definition = true,
        typeDefinition = true,
        callHierarchy = true,
        hover = true,
        rename = true,
        renameFileRefactoring = true,
        signatureHelp = true,
        codeAction = true,
        completion = {
          defaultTagNameCase = 'both',
          defaultAttrNameCase = 'kebabCase',
          getDocumentNameCasesRequest = false,
          getDocumentSelectionRequest = false,
        },
        schemaRequestService = true,
        documentHighlight = true,
        documentLink = true,
        codeLens = { showReferencesNotification = true },
        semanticTokens = true,
        diagnostics = true,
      },
      documentFeatures = {
        selectionRange = false,
        foldingRange = false,
        linkedEditingRange = true,
        documentSymbol = true,
        documentColor = true,
        documentFormatting = {
          defaultPrintWidth = 100,
          getDocumentPrintWidthRequest = true,
        },
      },
    },
    settings = {
      ['volar-api'] = {
        trace = {
          server = "off"
        }
      },
      ['volar-document'] = {
        trace = {
          server = "off"
        }
      },
      ['volar-html'] = {
        trace = {
          server = "off"
        }
      },
      volar = {
        codeLens = {
          references = true,
          pugTools = true,
          scriptSetupTools = true,
        },
        tagNameCase = 'both',
        attrNameCase = 'kebab',
        formatting = {
          printWidth = 100
        },
        autoCompleteRefs = true,
        preferredTagNameCase = 'auto',
        preferredAttrNameCase = 'auto-kebab',
      },
    };
  };
}
EOF

lua require'lspconfig'.volar.setup{}

endif

sorry,
I hove no time util now.
I try it,
thanks for your ,
i try it in my nvim-lsp config.
it can work .
It's amazing .
just some day.
I can use volar.
thanks.

[sethidden]

neovim/nvim-lspconfig#1223

[yaegassy]

Hi @3nuc

I think setting typescript in initializationOptions (nvim-lspconfig's init_options) is a must. Does the volar language server work correctly in your environment? neovim/nvim-lspconfig#1223

[sethidden]

Yeah it works for me. Do you have typescript installed globally? I wanted to avoid detecting installations like angularls does.

…

On September 5, 2021 7:07:46 PM GMT+02:00, yaegassy ***@***.***> wrote: Hi @3nuc I think setting typescript in initializationOptions (nvim-lspconfig's init_options) is a must. Does the volar language server work correctly in your environment? neovim/nvim-lspconfig#1223 -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #441 (comment)

[yaegassy]

Path to tsserver is hardcoded - looks like Volar autodetects tsserver - no need to provide path manually

The process of detecting typescript.js or tsserverlibrary.js in VSCode's volar extension is implemented on the client side, not on the Langauge Server side.

Of course, coc-volar and vim-lsp-settings also add the necessary processing on the client side.

In the case of nvim-lspconfig, I think you also need to use lspconfig/util or something similar to add processing like angular's settings. https://github.com/neovim/nvim-lspconfig/blob/master/lua/lspconfig/angularls.lua

[sethidden]

Ah, you're right, serverPath needs to be there. My local config was providing serverPath but once I switched to raw/pure config from nvim-lspconfig it's erroring out. Thanks!

[kshksdrt]

In hybrid mode, I do not get typescript intellisense inside the script tag of vue files.

Reproduction steps:

• Start with kickstart nvim.
• Modify the lsp config in init.lua like so.

  { -- LSP Configuration & Plugins
    'neovim/nvim-lspconfig',
    dependencies = {
      -- Automatically install LSPs and related tools to stdpath for Neovim
      'williamboman/mason.nvim',
      'williamboman/mason-lspconfig.nvim',
      'WhoIsSethDaniel/mason-tool-installer.nvim',

      -- Useful status updates for LSP.
      -- NOTE: `opts = {}` is the same as calling `require('fidget').setup({})`
      { 'j-hui/fidget.nvim', opts = {} },

      -- `neodev` configures Lua LSP for your Neovim config, runtime and plugins
      -- used for completion, annotations and signatures of Neovim apis
      { 'folke/neodev.nvim', opts = {} },
    },
    config = function()
      -- Brief aside: **What is LSP?**
      --
      -- LSP is an initialism you've probably heard, but might not understand what it is.
      --
      -- LSP stands for Language Server Protocol. It's a protocol that helps editors
      -- and language tooling communicate in a standardized fashion.
      --
      -- In general, you have a "server" which is some tool built to understand a particular
      -- language (such as `gopls`, `lua_ls`, `rust_analyzer`, etc.). These Language Servers
      -- (sometimes called LSP servers, but that's kind of like ATM Machine) are standalone
      -- processes that communicate with some "client" - in this case, Neovim!
      --
      -- LSP provides Neovim with features like:
      --  - Go to definition
      --  - Find references
      --  - Autocompletion
      --  - Symbol Search
      --  - and more!
      --
      -- Thus, Language Servers are external tools that must be installed separately from
      -- Neovim. This is where `mason` and related plugins come into play.
      --
      -- If you're wondering about lsp vs treesitter, you can check out the wonderfully
      -- and elegantly composed help section, `:help lsp-vs-treesitter`

      --  This function gets run when an LSP attaches to a particular buffer.
      --    That is to say, every time a new file is opened that is associated with
      --    an lsp (for example, opening `main.rs` is associated with `rust_analyzer`) this
      --    function will be executed to configure the current buffer
      vim.api.nvim_create_autocmd('LspAttach', {
        group = vim.api.nvim_create_augroup('kickstart-lsp-attach', { clear = true }),
        callback = function(event)
          -- NOTE: Remember that Lua is a real programming language, and as such it is possible
          -- to define small helper and utility functions so you don't have to repeat yourself.
          --
          -- In this case, we create a function that lets us more easily define mappings specific
          -- for LSP related items. It sets the mode, buffer and description for us each time.
          local map = function(keys, func, desc)
            vim.keymap.set('n', keys, func, { buffer = event.buf, desc = 'LSP: ' .. desc })
          end

          -- Jump to the definition of the word under your cursor.
          --  This is where a variable was first declared, or where a function is defined, etc.
          --  To jump back, press <C-t>.
          map('gd', require('telescope.builtin').lsp_definitions, '[G]oto [D]efinition')

          -- Find references for the word under your cursor.
          map('gr', require('telescope.builtin').lsp_references, '[G]oto [R]eferences')

          -- Jump to the implementation of the word under your cursor.
          --  Useful when your language has ways of declaring types without an actual implementation.
          map('gI', require('telescope.builtin').lsp_implementations, '[G]oto [I]mplementation')

          -- Jump to the type of the word under your cursor.
          --  Useful when you're not sure what type a variable is and you want to see
          --  the definition of its *type*, not where it was *defined*.
          map('<leader>D', require('telescope.builtin').lsp_type_definitions, 'Type [D]efinition')

          -- Fuzzy find all the symbols in your current document.
          --  Symbols are things like variables, functions, types, etc.
          map('<leader>ds', require('telescope.builtin').lsp_document_symbols, '[D]ocument [S]ymbols')

          -- Fuzzy find all the symbols in your current workspace.
          --  Similar to document symbols, except searches over your entire project.
          map('<leader>ws', require('telescope.builtin').lsp_dynamic_workspace_symbols, '[W]orkspace [S]ymbols')

          -- Rename the variable under your cursor.
          --  Most Language Servers support renaming across files, etc.
          map('<leader>rn', vim.lsp.buf.rename, '[R]e[n]ame')

          -- Execute a code action, usually your cursor needs to be on top of an error
          -- or a suggestion from your LSP for this to activate.
          map('<leader>ca', vim.lsp.buf.code_action, '[C]ode [A]ction')

          -- Opens a popup that displays documentation about the word under your cursor
          --  See `:help K` for why this keymap.
          map('K', vim.lsp.buf.hover, 'Hover Documentation')

          -- WARN: This is not Goto Definition, this is Goto Declaration.
          --  For example, in C this would take you to the header.
          map('gD', vim.lsp.buf.declaration, '[G]oto [D]eclaration')

          -- The following two autocommands are used to highlight references of the
          -- word under your cursor when your cursor rests there for a little while.
          --    See `:help CursorHold` for information about when this is executed
          --
          -- When you move your cursor, the highlights will be cleared (the second autocommand).
          local client = vim.lsp.get_client_by_id(event.data.client_id)
          if client and client.server_capabilities.documentHighlightProvider then
            vim.api.nvim_create_autocmd({ 'CursorHold', 'CursorHoldI' }, {
              buffer = event.buf,
              callback = vim.lsp.buf.document_highlight,
            })

            vim.api.nvim_create_autocmd({ 'CursorMoved', 'CursorMovedI' }, {
              buffer = event.buf,
              callback = vim.lsp.buf.clear_references,
            })
          end
        end,
      })

      -- LSP servers and clients are able to communicate to each other what features they support.
      --  By default, Neovim doesn't support everything that is in the LSP specification.
      --  When you add nvim-cmp, luasnip, etc. Neovim now has *more* capabilities.
      --  So, we create new capabilities with nvim cmp, and then broadcast that to the servers.
      local capabilities = vim.lsp.protocol.make_client_capabilities()
      capabilities = vim.tbl_deep_extend('force', capabilities, require('cmp_nvim_lsp').default_capabilities())

      require('mason').setup()
      local mason_registry = require('mason-registry')

      -- Enable the following language servers
      --  Feel free to add/remove any LSPs that you want here. They will automatically be installed.
      --
      --  Add any additional override configuration in the following tables. Available keys are:
      --  - cmd (table): Override the default command used to start the server
      --  - filetypes (table): Override the default list of associated filetypes for the server
      --  - capabilities (table): Override fields in capabilities. Can be used to disable certain LSP features.
      --  - settings (table): Override the default settings passed when initializing the server.
      --        For example, to see the options for `lua_ls`, you could go to: https://luals.github.io/wiki/settings/
      local servers = {
        -- clangd = {},
        -- gopls = {},
        -- pyright = {},
        -- rust_analyzer = {},
        -- ... etc. See `:help lspconfig-all` for a list of all the pre-configured LSPs
        --
        -- Some languages (like typescript) have entire language plugins that can be useful:
        --    https://github.com/pmizio/typescript-tools.nvim
        --
        -- But for many setups, the LSP (`tsserver`) will work just fine
        tsserver = {
          setup = {
            init_options = {
              plugins = {
                {
                  name = '@vue/typescript-plugin',
                  location = mason_registry.get_package("vue-language-server"):get_install_path() ..
                      '/node_modules/@vue/language-server',
                  languages = { 'vue' },
                },
              },
            },
            filetypes = { 'typescript', 'javascript', 'javascriptreact', 'typescriptreact', 'vue' },
          },
        },

        volar = {
          setup = {},
        },


        lua_ls = {
          -- cmd = {...},
          -- filetypes = { ...},
          -- capabilities = {},
          settings = {
            Lua = {
              completion = {
                callSnippet = 'Replace',
              },
              -- You can toggle below to ignore Lua_LS's noisy `missing-fields` warnings
              -- diagnostics = { disable = { 'missing-fields' } },
            },
          },
        },
      }

      -- Ensure the servers and tools above are installed
      --  To check the current status of installed tools and/or manually install
      --  other tools, you can run
      --    :Mason
      --
      --  You can press `g?` for help in this menu.

      -- You can add other tools here that you want Mason to install
      -- for you, so that they are available from within Neovim.
      local ensure_installed = vim.tbl_keys(servers or {})
      vim.list_extend(ensure_installed, {
        'stylua', -- Used to format Lua code
      })
      require('mason-tool-installer').setup { ensure_installed = ensure_installed }

      require('mason-lspconfig').setup {
        handlers = {
          function(server_name)
            local server = servers[server_name] or {}
            -- This handles overriding only values explicitly passed
            -- by the server configuration above. Useful when disabling
            -- certain features of an LSP (for example, turning off formatting for tsserver)
            server.capabilities = vim.tbl_deep_extend('force', {}, capabilities, server.capabilities or {})
            require('lspconfig')[server_name].setup(server)
          end,
        },
      }
    end,
},

I am sorry about the verbosity of the snippet.