You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 29, 2025. It is now read-only.
nvim-lspconfig only provides configs now and vim.lsp.enable() should be used instead, and the config should be passed to vim.lsp.config().
An additional benefit of this is that it prevents multiple LSP servers from being configured. mason-lspconfig.nvim automatically calls vim.lsp.enable() for LSP servers it installs, which currently results in 2 separate tailwind LSP servers being configured. (One with the lspconfig defaults and one with tailwind-tools.nvim's config.) I believe working around this in a user's config would require server.override = false and also manually setting up the configuration tailwind-tools.nvim would otherwise do. Using vim.lsp.config instead should prevent this.
Describe the bug
neovim/nvim-lspconfig/README.md#L39
nvim-lspconfigonly provides configs now andvim.lsp.enable()should be used instead, and the config should be passed tovim.lsp.config().An additional benefit of this is that it prevents multiple LSP servers from being configured. mason-lspconfig.nvim automatically calls
vim.lsp.enable()for LSP servers it installs, which currently results in 2 separate tailwind LSP servers being configured. (One with thelspconfigdefaults and one withtailwind-tools.nvim's config.) I believe working around this in a user's config would requireserver.override = falseand also manually setting up the configurationtailwind-tools.nvimwould otherwise do. Usingvim.lsp.configinstead should prevent this.