Occasional many errors in Neovim

[shellRaining]

I use Neovim as my editor, and today I configured vue_ls based on the wiki of this repository. My environment is as follows:

macOS 15.5
Neovim 0.11.3
nvim-lspconfig is the latest version
vue_ls 3.0.5
mason v2
treesitter main branch

The relevant configuration is as follows:

local lspconfig = {
  "neovim/nvim-lspconfig",
  config = function()
    local vue_language_server_path = vim.fn.expand("$MASON/packages")
      .. "/vue-language-server"
      .. "/node_modules/@vue/language-server"
    local vue_plugin = {
      name = "@vue/typescript-plugin",
      location = vue_language_server_path,
      languages = { "vue" },
      configNamespace = "typescript",
    }
    local vtsls_config = {
      settings = {
        vtsls = {
          tsserver = {
            globalPlugins = {
              vue_plugin,
            },
          },
        },
      },
      filetypes = { "typescript", "javascript", "javascriptreact", "typescriptreact", "vue" },
    }
    local vue_ls_config = {}
    vim.lsp.config("vtsls", vtsls_config)
    vim.lsp.config("vue_ls", vue_ls_config)
    vim.lsp.enable({ "vtsls", "vue_ls" })
  end,
}

LSP log below:

[START][2025-08-03 19:09:39] LSP logging initiated
[ERROR][2025-08-03 19:09:39] ...lsp/handlers.lua:562	"Execute command typescript.tsserverRequest failed: Error: <semantic> TypeScript Server Error (5.8.3)"
[ERROR][2025-08-03 19:09:39] ...lsp/handlers.lua:562	"Execute command typescript.tsserverRequest failed: Error: <semantic> TypeScript Server Error (5.8.3)"
[ERROR][2025-08-03 19:09:39] ...lsp/handlers.lua:562	"Execute command typescript.tsserverRequest failed: Error: <semantic> TypeScript Server Error (5.8.3)"
[ERROR][2025-08-03 19:09:39] ...lsp/handlers.lua:562	"Execute command typescript.tsserverRequest failed: Error: <semantic> TypeScript Server Error (5.8.3)"

Has anyone encountered a similar situation, and how should I resolve it?

[RayGuo-ergou]

This general caused by vue plugin not properly loaded. Are you using mason lspconfig plugin? it automatically enable the lsps, maybe your nvimlspcofing here loaded after that.

[shellRaining]

yes, I'm using mason lspconfig plugin v2, I will have a try this weeekend, thank you

[luigiMinardi]

I was with the same problem as you, I was trying to debug it with vim.lsp.set_log_level("debug"), removing and adding ts_ls and vue_ls, tried adding filetypes = 'vue' to vue_ls and removing vue from ts_ls filetypes, uninstalled ts_ls and tried only vue_ls, uninstalled vue_ls and tried only ts_ls, tried vtsls instead of ts_ls, tried both at the same time.

Somehow after many trial and error I got back to an error saying "Could not find ts_ls or vtsls, required by vue_ls." and re-adding the configs like this worked. I dunno why nor how, but I hope my config may help your debug.

I also have my full config repo if that helps

-- Configuring Vue LSP
local vue_language_server_path = vim.fn.stdpath('data') ..
    '/mason/packages/vue-language-server/node_modules/@vue/language-server'

local servers = {
    -- other servers here
    ts_ls = {
        init_options = {
            plugins = {
                {
                    name = '@vue/typescript-plugin',
                    location = vue_language_server_path,
                    languages = { 'vue' },
                    configNamespace = 'typescript',
                },
            },
        },
        filetypes = { 'typescript', 'javascript', 'javascriptreact', 'typescriptreact', 'vue' },
    },
    vue_ls = {},
}

require('mason').setup()

-- Ensure the servers above are installed
local mason_lspconfig = require 'mason-lspconfig'

mason_lspconfig.setup {
    ensure_installed = vim.tbl_keys(servers or {}),
    automatic_enable = true
}

for server_name, config in pairs(servers) do
    vim.lsp.config(server_name, config)
end

[meseck]

I had the same problem with the same error message:
Execute command typescript.tsserverRequest failed: Error: <semantic> TypeScript Server Error (5.8.3)

I was able to fix this by additionally setting “enableForWorkspaceTypeScriptVersions” = true:

{
  name = "@vue/typescript-plugin",
  location = vue_language_server_path,
  languages = { "vue" },
  configNamespace = "typescript",
  enableForWorkspaceTypeScriptVersions = true,
}

The vtsls readme recommends this for plugins that are installed outside the project:
https://github.com/yioneko/vtsls/blob/main/README.md#typescript-plugin-not-activated

You can find more information about this setting here: microsoft/vscode#65031

It seems that the version bump of typescript caused the problem? 3d68967

[ahas]

This might be a simpler problem than expected.
Please check if the environment variable $MASON is set.
If it's not set... yes, you would need to set it,

[RayGuo-ergou]

$MASOn is set when mason.nvim init, not need manually set from user, if not using mason then should not use this env.

[ahas]

$MASOn is set when mason.nvim init, not need manually set from user, if not using mason then should not use this env.

I'm an NvChad user and I just confirmed that NvChad has Mason's PATH option set to 'skip'.
If PATH is not 'append' or 'prepend', setting it manually seems to be the correct approach.

[RayGuo-ergou]

I see, not familiar with nvchad, thanks