nvim-lspconfig/lsp, branch master

doc(ts)ls): installation instructions #4517

2026-09-06T18:40:19Z

feat(clice): clice #4522

2026-09-04T10:31:22Z

fix(esbonio): use version 2 CLI #4516

2026-08-30T22:26:48Z

Problem: The Python module command bypasses standalone uv and pipx installations, and the configuration examples target Esbonio 0.16. Solution: Launch the public Esbonio 2 CLI, recognize conf.py as a project root, and document the current project configuration model.

fix(powershell_es): validate shell, no profile #4513

2026-08-28T10:11:56Z

- Check that `shell` (or the default `pwsh`) is executable before building the command; log and abort cleanly via `cmd() -> nil` instead of spawning a broken process. Note: `cmd() -> nil` requires a core Neovim fix (see neovim/neovim#41479), which makes `Client.create` return `nil, err` instead of crashing when `cmd()` returns nil. Without that fix, this bail-out path will error on current Neovim releases. - Fall back to dynamically resolving the PowerShellEditorServices module path via `Get-Module -ListAvailable` when `bundle_path` is not set, instead of requiring it to be configured explicitly. - Default `init_options.enableProfileLoading` to `false`. The server runs as a background process, not an interactive session, and a user profile that writes to stdout can corrupt the LSP stdio handshake. Overridable via `init_options` in `vim.lsp.config()`. Note: this is distinct from the already-documented `settings.powershell.enableProfileLoading` in lua/lspconfig/types/lsp/powershell_es.lua, which configures VS Code's `workspace/configuration` response and defaults to `true` there. `init_options.enableProfileLoading` is read once at server startup (see PowerShell/PowerShellEditorServices#1801) and cannot be changed via `settings` afterward. - Document the new default and override in the `@brief` header. Only lsp/powershell_es.lua is touched. lua/lspconfig/configs/powershell_es.lua is left as-is (deprecated, Nvim <=0.10 only, slated for deletion). lua/lspconfig/types/lsp/powershell_es.lua is an auto-generated type stub for `settings.*` and is unrelated to this change.

fix(ast_grep): attach to shell buffers #4514

2026-08-27T10:20:03Z

fix(rust_analyzer): show non-error msg if rustc/cargo are missing #4500

2026-08-24T14:36:04Z

feat: rust_glancer #4512

2026-08-24T10:38:15Z

feat: ms_terraform_lsp #4510

2026-08-24T09:22:29Z

fix(ols): skip config if missing "odin" command #4511

2026-08-21T22:46:50Z

Problem: Current config throws an error if 'odin' is not on the PATH. Solution: Check its availability with executable().

fix(oxc): allow oxfmt and oxlint to run in single-file mode #4509

2026-08-19T18:24:39Z

Problem: The `oxlint` and `oxfmt` servers don't get started if a root directory can't be determined. I think the change which added these servers (originally they were both in `oxc-language-server`) https://github.com/neovim/nvim-lspconfig/pull/3586 either cargo culted `single_file_support = true` from the `biome` config or there was no single-file support at the time (I only started using `oxfmt` today). Either way, single-file mode is explictly supported now: https://github.com/oxc-project/oxc/blob/f7be7cc5d3011203da2d824be18d6980adc786ba/crates/oxc_language_server/src/backend.rs?plain=1#L141. Solution: Remove `workspace_required = true` from the `oxlint` and `oxfmt` configs. I've tested `oxfmt` in single-file mode on a HTML, JS, TS, and markdown file. I've tested `oxlint` in single-mode on a JS file.

feat: php_lsp #4489

2026-08-19T09:21:54Z

Adds support for php-lsp, a PHP language server written in Rust. See: https://github.com/jorgsowa/php-lsp

fix(slang-server): use nearest dir with any marker as a workspace root #4508

2026-08-18T20:49:21Z

**Problem** Workspace search always converges to the project repo root dir (that has `.git`) regardless of presence of `.slang/` in any of subdirs. This makes it impossible to properly detect individual workspaces in monorepo projects. E.g. see https://github.com/EECS-151/fpga-labs-sp26. Each of `labX/` directories is essentially a separate workspace. Adding `labX/.slang` with workspace config has no effect as `.git` marker is of higher priority and is guaranteed to be found at the repo root, leading to incorrect workspace root resolution. **Solution** Whenever possible, give both markers the same priority. So that for multi-workspace repos workspace search will stop at the first `.slang` config rather than at the root `.git`. Nothing has changed for single workspace projects that either have or don't have .slang config at repo root.

feat: symfony_lsp #4507

2026-08-18T14:53:04Z

fix(tsc): skip binaries that do not support --lsp #4505

2026-08-17T21:48:54Z

fix(vhdl_ls): drop .vhdl_ls.toml root marker #4506

2026-08-17T21:37:59Z

Problem: `.vhdl_ls.toml` is listed as a root marker, but vhdl_ls only reads that file from the user's home directory, never from a project directory. When it is present, root_dir resolves to $HOME for any VHDL file underneath it. Solution: Remove `.vhdl_ls.toml` from root_markers.

feat(tsc): enable CodeLens #4501

2026-08-17T06:07:51Z

fix(julials): fix the default setup #4499

2026-08-13T13:13:02Z

This patch updates the julials config: - Drop explicit installation and loading of SymbolServer and StaticLint (these are/were dependencies of LanguageServer and it was never required to load them at this top level anyway). - Drop the project path handling. This is only used for standalone files now, and the LanguageServer itself makes a good job of determining it. - Use LanguageServer.runserver() to start the server instead of the internal run(LanguageServerInstance(...)) path. The latter is broken since https://github.com/julia-vscode/LanguageServer.jl/commit/eb9eb72a10467dd951f605090ca3f144c74cecee (see e.g. https://github.com/julia-vscode/LanguageServer.jl/issues/1408) because of updated arguments to the LanguageServerInstance default constructor.

feat: tsc #4493

2026-08-12T14:06:02Z

Problem: `tsgo` was a temporary executable available as a preview version for the Typescript 7.0 Go rewrite. Now that Typescript 7.0 has been released, the `tsgo` executable name and project are being rolled back into the main Typescript project. As of that release, the standard executable is installed from `npm` via the name `typescript`, and executable itself is named `tsc`. Solution: Deprecate `tsgo` as a language server name, and instead configure a more appropriately named language server that supports the permanent `tsc` executable name in addition to the `tsgo` executable name to keep backward compatibility. The only changes are names, docs, and within the `cmd` for `tsc`, support for both the `tsc` and `tsgo` executable names, with a preference for `tsc`.

fix(verible): add verible.filelist as root marker #4498

2026-08-12T14:02:30Z

Problem: verible-verilog-ls's README documents verible.filelist as the marker for the project root, but root_markers only contains .git. In a project where verible.filelist isn't co-located with .git, root_dir resolves to the wrong (ancestor) directory. Solution: Add verible.filelist ahead of .git in root_markers, matching the priority already used in vhdl_ls.lua, ghdl_ls.lua, and svlangserver.lua, and matching the marker the upstream README itself documents. Verified: with only .git as marker, root_dir resolved to the .git ancestor above the actual project directory. With verible.filelist added, root_dir correctly resolves to the directory containing it. Confirmed both directions via vim.lsp.get_clients()[1].root_dir in an isolated NVIM_APPNAME harness pointed at this branch.

feat: pkl #4495

2026-08-11T08:26:40Z

fix(vhdl_ls): require workspace #4494

2026-08-11T08:18:07Z

Problem: vhdl_ls rejects initialization without a rootUri. Opening a VHDL file outside a project starts a client with root_dir=nil that emits three errors and produces no diagnostics. Solution: Set workspace_required so the client only starts when a vhdl_ls.toml or .vhdl_ls.toml is found.

fix(ols): reuse existing client when opening libraries #4491

2026-08-04T18:51:15Z

Problem: When going to the definition of a library function, a new ols client is created. Solution: Detect if the file is a library. If so, re-use a pre-existing client.

docs(emmylua_ls): remove irrelevant issue link #4490

2026-08-01T10:07:15Z

emmylua_ls deduplicates all workspace files before analysing them. Therefore, using the recommended `workspace.library = vim.api.nvim_get_runtime_file("", true)` will not result in erroneous duplicate field warnings as discussed in #3189.

feat(oxfmt): enable for svelte #4488

2026-07-31T09:08:19Z

fix(roslyn_ls): iter() expects a table #4487

2026-07-28T20:39:31Z

docs(astro): TypeScript 7.x limitation, npm-global fallback (#4486)

2026-07-26T10:21:41Z

docs(astro): update language-tools URLs #4485

2026-07-23T11:01:00Z

feat: agentscript #4483

2026-07-23T10:42:40Z

refactor!: drop `lsp/rls.lua` #4481

2026-07-21T13:03:10Z

https://github.com/rust-lang/rls has been archived since 2022, so this vestigial config does more harm than good.

fix(ast_grep): stop reuse_client from spawning duplicate lsp client #4480

2026-07-20T23:28:16Z

Problem: Old config set config.cmd_cwd = config.root_dir inside reuse_client itself. On the first client's initial start, reuse_client is never invoked (nothing exists yet to compare against), so cmd_cwd is never set on it. On the second start attempt, the comparison client.config.cmd_cwd == config.cmd_cwd evaluates nil == , which fails, and a second client spawns. Solution: Change reuse_client key-value pair to reuse_client = function(client, config) return client.name == config.name and client.config.root_dir == config.root_dir end, Now the first spawned client is reused. Only one lua_ls client was ever spawned. Only the `reuse_client` section looked fishy to me.

fix(eslint): convert workspaceFolder.uri to a proper URI #4479

2026-07-20T13:06:50Z

feat(pyright): disable tagged hints by default #4478

2026-07-17T17:20:59Z

Problem: Pyright marks unreachable, unreferenced and deprecated code with hint diagnostics. Nvim correctly reports them as regular diagnostics, but they are usually too noisy (c.f., neovim/neovim#30444). Solution: Disable it by default in pyright and basedpyright for a better default user experience.

docs(docker-language-server): typo #4477

2026-07-16T14:10:57Z

fix(roslyn_ls): update diagnostics on project/solution initialization #4474

2026-07-13T12:53:27Z

Problem: When a solution or a project gets loaded, diagnostics do not update correctly. Solution: Change refresh_diagnostics function. Instead of performing one `client:request`, call `client:request` for every capability registered by roslyn for diagnosticProvider.

feat: terragrunt-ls #4473

2026-07-12T18:50:24Z

feat: pytest-language-server #4472

2026-07-11T12:41:37Z

feat: wolfram_lsp #4471

2026-07-11T12:05:51Z

docs: qmlls6 #4470

2026-07-11T12:02:53Z

Some distros like arch have a separate package with a cmd of qmlls6.

feat: kdl_lsp #4468

2026-07-10T13:34:37Z

docs(angularls): update link to angularls #4466

2026-07-04T10:28:36Z

fix(ruff_lsp): deprecate `ruff_lsp` in favour of `ruff` #4463

2026-07-01T17:07:01Z

Problem: ruff_lsp project is now archive and the tool deprecated Solution: add deprecation warning to the config description, also ensure that the user is warned when enabling the config using `vim.deprecate()`

fix(svelte): support svelteserver installed in node_modules #4462

2026-06-30T18:55:51Z

Problem: Currently the `svelte` configuration expects a globally installed `svelteserver` binary. Meanwhile, other LSP configs support binaries installed as dev dependencies on `node_modules/.bin`. A global language server makes it harder to have project-scoped version management. Solution: Implement a `cmd` finder similar to `oxlint` and `oxfmt` which considers `node_modules/bin` as an additional lookup path as well as the global install Workaround: Meanwhile, users can define the `cmd` function on their own `vim.lsp.config('svelte')` as needed.

Enable clangd lsp for c.doxygen / cpp.doxygen #4459

2026-06-25T17:57:49Z

This fixes #4458. One option to get doxygen highlighting in C / C++ files is to append `.doxygen` to the file type (see `:help doxygen`). This commits add the `c.doxygen` / `cpp.doxygen` filetypes to the list of clangd lsp to be compatible with this approach. Note that vim help also recommend an alternative approach that doesn't change the filetype, which is to define the variable: let g:load_doxygen_syntax=1

fix(hhvm): run server in project root #4456

2026-06-19T15:00:13Z

added µcad lsp #4454

2026-06-18T22:54:53Z

feat(terraformls): enable codelens #4453

2026-06-18T13:03:17Z

ref https://github.com/hashicorp/terraform-ls/blob/84064cd19ffd0d6b356cd2725d81987111c94cb6/docs/language-clients.md#L162

feat: fallow lsp #4450

2026-06-12T20:43:01Z

docs: update link to opencl_ls documentation #4451

2026-06-12T20:42:27Z

fix(gitlab_duo): update npm registry command for GitLab LSP #4449

2026-06-08T16:38:40Z

Make registry path more specific to the main package to make npx command more reliable Upstream issue: https://gitlab.com/gitlab-org/editor-extensions/gitlab-lsp/-/work_items/2371

fix(emmylua_ls): move settings under emmylua section #4447

2026-06-03T15:05:33Z

Problem: EmmyLua requests configuration from the "emmylua" section, but the current configuration doesn't expose the settings under that section. Example request and response: ```json { "jsonrpc": "2.0", "id": 1, "method": "workspace/configuration", "params": { "items": [ { "scopeUri": "file:///Users/marcus/.dotfiles", "section": "emmylua" } ] } } ``` ```json { "result": [ null ], "id": 1, "jsonrpc": "2.0" } ``` Solution: Move the settings under the "emmylua" section. After these changes: ```json { "jsonrpc": "2.0", "id": 1, "method": "workspace/configuration", "params": { "items": [ { "scopeUri": "file:///Users/marcus/.dotfiles", "section": "emmylua" } ] } } ``` ```json { "result": [ { "hint": { "enable": true }, "codeLens": { "enable": true } } ], "id": 1, "jsonrpc": "2.0" } ```

feat: cqlls #4444

2026-06-02T12:57:19Z

feat(gopls): semantic tokens enabled by default on client side (#4446)

2026-06-02T11:52:42Z

feat(oxlint): check if tsgolint bin exists inside project #4437

2026-05-28T17:17:27Z

feat(jls): add jls config #4439

2026-05-28T17:14:06Z

Co-authored-by: Delice0 <59118341+Delice0@users.noreply.github.com>

fix(rescript): default parameters do not enable incrementalTypechecking #4440

2026-05-28T17:13:01Z

Fixes the issue by changing "enabled" to "enable"

fix(flow): resolve project-local binary before npx fallback #4431

2026-05-28T17:11:44Z

When flow is not in global PATH, try node_modules/.bin/flow relative to the project root before falling back to npx. This covers the common case where flow-bin is a local devDependency.

feat: slang-server #4441

2026-05-27T14:05:09Z

docs(roslyn_ls): dotnet tool install instructions #4435

2026-05-22T08:42:33Z

fix(roslyn_ls): drop unnecessary code, recommend maintained plugin #4436

2026-05-22T08:25:49Z

rzls.nvim is deprecated and the support of razor is now moved into roslyn.nvim with the author for rzls.nvim joining to maintain roslyn.nvim

fix(oxc): fix oxlint, oxfmt vite plus config search #4434

2026-05-21T14:36:13Z

fix(ruby-lsp): broken `reuse_client` logic #4433

2026-05-20T20:21:40Z

avoid spawning extra LSP instances by fixing the reuse_client logic.

feat: shuck language server #4417

2026-05-18T22:21:40Z

shuck is a lightning fast shell linter and language server written in Rust. It supports bash, zsh, posix, and mksh dialects. https://github.com/ewhauser/shuck

feat: update oxfmt, oxlint to detect vite plus #4395

2026-05-18T09:39:16Z

Problem: oxfmt and oxlint have the ability to use vite plus config, as mentioned here: https://github.com/voidzero-dev/vite-plus/issues/629 Solution: update the configs to reflect that.

feat(zizmor): attach to action.yaml #4430

2026-05-16T14:21:30Z

Problem: Only matching `action.yml` Solution: Match `action.yaml` also.

docs(emmylua_ls): fix docstring #4428

2026-05-14T20:28:59Z

feat(harper_ls): add tex filetype #4427

2026-05-14T20:06:11Z

docs(emmylua_ls): fix config example #4426

2026-05-14T12:08:18Z

feat: hare-lsp #4425

2026-05-14T11:59:24Z

feat: improve emmylua_ls #4423

2026-05-12T14:33:22Z

Problem: `emmylua_ls` is emerging as the preferred Lua LS for Neovim, but the config provided by nvim-lspconfig is almost useless. Solution: Update the config to provide hints similar to that of `lua_ls`.

feat(dexter): dexter LSP for large Elixir codebases #4421

2026-05-12T13:31:10Z

fix: logic bugs found by AI

2026-05-07T17:44:33Z

1. `plugin/lspconfig.lua`: LspRestart timer was never closed after firing, leaking a libuv handle on every invocation. 2. `lsp/muon.lua`: Formatting cmd (a list) with %s, producing table: 0x... instead of the command.

feat: panache language server (#4418)

2026-05-07T12:40:02Z

Panache is a language server (formatter, and linter) for Markdown, Quarto, and R Markdown. It's built in Rust and uses a lossless CST parser. It supports integrating external formatters and linters. It's packaged at crates.io, NPM, PyPi, and as a VSIX extension at VS Code Marketplace and Open VSX. Binaries are provided directly from the GitHub repo.

fix(kotlin_lsp): update cmd to `intellij-server` #4412

2026-04-30T00:45:45Z

per https://github.com/Kotlin/kotlin-lsp/commit/75ddb7586e0170ed93912b0be5d67e0a45769ee6 , the new name of the launcher is `intellij-server`, not `kotlin-lsp`.

fix(esbonio): update cmd for esbonio v2 #4409

2026-04-29T11:38:36Z

Esbonio v2 can no longer be started with the top-level esbonio command. Switch to 'esbonio.server' which is compatible with v1 and v2. See: https://github.com/swyddfa/esbonio/pull/1098

fix(ast_grep, ruby_lsp): check name in reuse_client #4408

2026-04-28T22:22:38Z

fix(spade_ls): default binary name #4404

2026-04-27T12:59:41Z

feat: spade_ls #4403

2026-04-27T10:14:02Z

docs: update expert repo #4402

2026-04-27T10:12:50Z

The repo moved from elixir-lang to expert-lsp (https://github.com/expert-lsp/expert)

feat: ctags_lsp #4399

2026-04-23T14:25:23Z

docs(lua_ls): how to include lspconfig types #4396

2026-04-21T11:21:11Z

feat: phpantom_lsp #4362

2026-04-20T09:42:14Z

fix(flow): invalid condition #4394

2026-04-16T08:55:45Z

fix(groovyls): use global executable instead of local jar #4392

2026-04-15T23:05:32Z

fix(golangci_lint_ls): guard against missing `golangci-lint` in `before_init` (#4390)

2026-04-15T04:20:39Z

feat: zizmor #4382

2026-04-12T19:14:33Z

fix(gdscript): remove invalid filetypes #4387

2026-04-12T15:38:59Z

Problem: 'gd' and 'gdscript3' are file extentions, not filetypes (as per the result of running `getcompletion('', 'filetype')` command in neovim Solution: Remove them, leaving only 'gdscript'

feat: use node_modules local executable if available #4386

2026-04-12T15:00:06Z

feat(smithy_ls): bump from 0.7.0 to 0.8.0 #4385

2026-04-12T12:48:55Z

feat(buf_ls): buf-config filetype #4384

2026-04-10T14:15:03Z

The next release of `buf` will include LSP features that include support for buf config files. This follows the approach that other LSPs follow for specifying custom filetypes (a comment + adding that custom filetype to filetypes).

fix(oxlint): oxlintrc.jsonc root marker #4381

2026-04-08T20:38:52Z

feat: csskit #4380

2026-04-08T15:44:02Z

docs(gitlab_duo): outdated docs (#4377)

2026-04-05T16:08:51Z

fix(tailwindcss): revert broken config detection #4376

2026-04-05T14:33:03Z

Problem: `find_tailwind_global_css` attempted to address #4204, where `experimental.configFile` was set using the return value of `vim.fs.find()`. The language server rejected this with `Invalid experimental.configFile configuration, not initializing` because `configFile` expects either a string or a key-value record (object), not an array/list. This was a syntax issue, not a detection issue. Using the correct syntax for `configFile` in Lua should be sufficient to address the original issue. Right now, `find_tailwind_global_css` always runs for users who haven't explicitly set `configFile` — overriding the LSP's native detection and **forcing anyone who wants to opt out to manually set all entry-points by hand.** Solution: - Remove `find_tailwind_global_css` entirely and restores `configFile` to its default `nil` so the `tailwindcss` LSP handles project detection natively. - Simplify `before_init` based on [this suggestion from the initial PR](https://github.com/neovim/nvim-lspconfig/pull/4222#discussion_r3018499628). The following syntax worked for me while testing to explicitly set the `configFile` based on the [official docs](https://github.com/tailwindlabs/tailwindcss-intellisense#tailwindcssexperimentalconfigfile) for single entry-point: > [!NOTE] > Single entry-point is resolved relative to the workspace root (`root_dir` — verify with `:checkhealth vim.lsp`) ```lua vim.lsp.config('tailwindcss', { settings = { tailwindCSS = { experimental = { -- v3: config file configFile = 'tailwind.config.js', -- v4: CSS entry-point -- configFile = 'src/styles/app.css', }, }, }, }) ``` For projects with multiple entry-points, or different projects, the following syntax can be used for multiple entry-points: > [!NOTE] > Keys are relative to `root_dir` as above, but from my testing on macOS, absolute paths worked better ```lua vim.lsp.config('tailwindcss', { settings = { tailwindCSS = { experimental = { configFile = { ['tailwind.config.js'] = '/Users/username/path/to/project-a/**', ['src/main.css'] = '/Users/username/path/to/project-b/**', }, }, }, }, }) ``` #### Project or Local Configuration For project-specific settings without modifying your global Neovim config: 1. Enable in your Neovim config: ```lua vim.o.exrc = true ``` 2. Create `.nvim.lua` in the project root: ```lua vim.lsp.config('tailwindcss', { settings = { tailwindCSS = { experimental = { configFile = 'tailwind.config.ts', }, }, }, }) ``` 3. Open `.nvim.lua` and run `:trust` to allow the file, then restart Neovim. 4. Verify with `:checkhealth vim.lsp`.

feat(tailwindcss): support multiple import patterns #4371

2026-04-03T18:43:21Z

feat(robotcode): support virtual env #4367

2026-04-03T15:01:32Z

feat: make oxfmt support oxfmt.config.ts files (#4372)

2026-04-03T14:54:59Z

fix(tailwindcss_ls): add experimental.configFile to support Tailwind v4 #4222

2026-03-31T21:20:42Z

fix(biome): set lower priority for config files as root #4363

2026-03-28T12:10:33Z

fix(roslyn_ls): handle roslyn.client.fixAllCodeAction command #4358

2026-03-27T10:42:34Z

feat(stylelint)!: migrate to stylelint-language-server #4351

2026-03-26T09:54:19Z

stylelint now has an official LS: [@stylelint/language-server](https://github.com/stylelint/vscode-stylelint/tree/main/packages/language-server)