Warning showing when requiring the ('mason.lspconfig').setup

[nehamand]

Before Reporting an Issue

• I have read the kickstart.nvim README.md.

• I have read the appropiate plugin's documentation.

• I have searched that this issue has not been reported before.

• [x ] By checking this, I confirm that the above steps are completed. I understand leaving this unchecked will result in this report being closed immediately.

Describe the bug

On line 669 on the init.lua file, there is a warning stating that the mason.lspconfig setup is missing required fields in type MasonLspconfigSettings: ensure_installed, automatic_installation [missing-fields].

To Reproduce

1. Just clone the repo and open it in neovim, go the line 669 and you will see the lua-lsp pointing to the warning.

Desktop

• OS: Mac Os Sequoia 15.1
• Terminal: Warp

Neovim Version

0.10.3

[BALAJI24092001]

I have the same issue, the LSP for lua seems to generate those warnings. There won't be any problem with the highlighted warnings. But I wouldn't want them to pop on screen either. I added the ensure_installed = {} which removed one warning, but the other one I didn't. It should probably work. Add them and leave them blank.

[nhld]

Hi,
You might want to uncomment this line:

kickstart.nvim/init.lua

Lines 639 to 645 in db4867a

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

Hope this helps!

[feoh]

@nhld Should we consider uncommenting this by default?

I feel like we get a constant stream of these issues, all well meant, and I don't blame folks for filing them, but they're kinda noise.

What's the down side if any?

[BALAJI24092001]

I suppose uncommenting is better. It could be confusing for beginners to see unnecessary warnings. It doesn't seem to have any downside so far for me.

[feoh]

No, the warnings are essentially meaningless, but they cause well meaning folks to file bug after bug after bug :)

Let me ask the same question from a different angle: Does having these warnings benefit anyone ever?

[BALAJI24092001]

They do.

kickstart.nvim/init.lua

Lines 639 to 645 in db4867a

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

I suppose a comment of this sort can benefit either groups of people. Since it's in mason-lspconfig, adding an extra line can be a benefit.

[nhld]

How about using ---@diagnostic disable-next-line: missing-fields to suppress the warning? We can have a warning-free init.lua without disabling diagnostics. We can remove the diagnostics disable comments later when the upstream plugin's author or contributors make those fields optional.

Do we have to disable it? The suggested approach seems to get the job done as well.

[pythoncarpenter]

Hey, I’m a bit late to this conversation, but here’s a quick fix:

The warning about missing required fields (ensure_installed and automatic_installation) happens because those fields aren’t explicitly provided—even though Kickstart uses mason-tool-installer to handle installs. To silence the warning without affecting behavior, you can update your config like so:

require('mason-lspconfig').setup({
ensure_installed = {}, -- explicitly set to an empty table (Kickstart populates installs via mason-tool-installer)
automatic_installation = false,
handlers = { ... } -- (handlers as defined by Kickstart for auto-setting up servers)
})

This should clear up the type warnings and keep everything working as expected.

[feoh]

@pythoncarpenter Hey, better late than never, and I LOVE your proposed fix! I created a PR for it.

Not seeing any problems so far but would love others to test with their configurations.

[feoh]

@pythoncarpenter @BALAJI24092001 Would you folks be willing to give my pull request a look and maybe even try the change and see what you think?

I need somebody to approve it as I don't want to just cowboy everything and merge my changes without a second set of eyes. Not good practice :)

[pythoncarpenter]

1. What is the test to determine if automatic installation = false doesn't break anything

2.   require('mason-tool-installer').setup { ensure_installed = ensure_installed }
   

Is the line above require('mason-lspconfig').setup {

Does empty table {} clear the variable for Kickstart.nvim and points to vim.tbl_keys(servers or {})?

TBH---I just implemented the change from o3-mini-high--pretty happy I stopped seeing the orange and called it a day.

[feoh]

The danger of AI made manifest :)

(I use and love it too so no judgement!)

But we should probably work to understand what we're doing here and answer your questions :)

[feoh]

The docs for the automatic install parameter are here.

Seems like it just controls whether LSPs you installed via lspconfig show up as installed already in Mason maybe?

[pythoncarpenter]

I'll take a look at it tomorrow

[haxybaxy]

Maybe lua should be added to ensure_installed? It also provides for a sensible default and gives users intuition about how the ensure_installed table is used

[feoh]

Just merged the PR with crossed fingers :) Closing.

[blob42]

The latest Mason 2.0 removed all handlers related settings. Here is the config that I use now for my LSP that is compatible with the latest mason and lspconfig.

local capabilities = vim.lsp.protocol.make_client_capabilities()
capabilities = vim.tbl_deep_extend('force', capabilities, require('cmp_nvim_lsp').default_capabilities())

-- dict of your custom lsp server configs 
local servers = require 'custom.lsp.servers'

-- list of lsp servers to manually manage
local manual_lspconfig = { 'rust_analyzer' }

require('mason').setup()

local ensure_installed = vim.tbl_filter(function(sname)
  return not vim.tbl_contains(manual_lspconfig, sname)
end, 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 {
  ensure_installed = {}, -- explicitly set to an empty table (Kickstart populates installs via mason-tool-installer)
  automatic_enable = {
    exclude = {
      'rust_analyzer',
    },
  },
}

vim.lsp.config('*', {
  capabilities = capabilities,
})

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

local rusta = require 'rustaceanvim.config.server'
vim.lsp.config('rust-analyzer', {
  capabilities = vim.tbl_deep_extend('force', rusta.create_client_capabilities(), require('cmp_nvim_lsp').default_capabilities()),
})
vim.lsp.enable 'rust-analyzer'