nvim-lspconfig

Status: 🌿

Problem

Need consistent language server integration across multiple stacks with minimal per-project setup.

Why This Choice

• Standard Neovim LSP integration layer with broad language support.
• Works directly with mason.nvim and mason-lspconfig.nvim for installation and lifecycle management.

Current Usage

• Active servers: cssls, eslint, lua_ls, phpactor, tsserver, vuels.
• Integrated with diagnostics, formatting flow, and symbol/reference navigation.

Keybindings in Use

• K: hover.
• Space l r: rename.
• Space l a: code actions.
• Space l s: document symbols.
• Space l e: references.

Caveats

• Server capabilities can differ by language and project conventions.
• Keep formatter/linter ownership explicit when combining LSP with none-ls.

Removal Criteria

• If Neovim core or another orchestration layer provides better reliability with less config overhead, migrate.