Loading nvim/lspconfig so that the lsp folder overrides the plugin defaults

[richardmarbach]

I've been scratching my head for a while and can't seem to find any resources in the related repos or docs.

Versions:

• neovim 0.11.3
• lazy.nvim 6c3bda4aca61a13a9c63f1c1d1b16b9d3be90d7a

My goal is to load nvim/lspconfig so that it respects the load order of the new lsp/* configuration folders. I'm currently adding lspconfig in a separate file in my plugins folder:

 return {
  {
    "neovim/nvim-lspconfig",
    lazy = false,
    setup = function()
      vim.lsp.config("ts_ls", {
        cmd = { "mise", "x", "bun@latest", "--", "bunx", "--bun", "typescript-language-server", "--stdio" },
      })
    end,
  }
}

I've also got the same configuration in lsp/ts_ls.lua:

return {
        cmd = { "mise", "x", "bun@latest", "--", "bunx", "--bun", "typescript-language-server", "--stdio" },
}

I've already tried moving the lsp configuration into the setup function, since the docs for the lsp suggest that they are merged last. However, when I print the loaded ts_ls configuration, I still get the lspconfig defaults:

 cmd = { "typescript-language-server", "--stdio" },

Would love some pointers on where I'm going wrong!

[richardmarbach]

I was using the incorrect option. You want config:

return {
  {
    "neovim/nvim-lspconfig",
    config = function()
      vim.lsp.config("ts_ls", {
        cmd = { "mise", "x", "bun@latest", "--", "bunx", "--bun", "typescript-language-server", "--stdio" },
      })
      vim.lsp.enable("ts_ls")
    end,
  }
}```