Composer LSP

Composer LSP

Composer LSP adds package navigation and version information to composer.json files in Zed and Neovim. The language server is written in Rust and does not require Composer or a JavaScript runtime in the background.

Features

• Command-click a dependency to open its Packagist page.
• Show the installed version next to its constraint.
• Show when a newer stable release is available.
• Read Composer 1 and Composer 2 installation metadata.
• Respect a custom config.vendor-dir.
• Leave Zed's built-in JSON formatting and validation untouched.

Package links work in require, require-dev, conflict, replace, provide, and suggest. Platform requirements such as php, ext-*, and lib-* are ignored because they are not Packagist packages.

Zed

Install Composer LSP from Zed's Extensions page.

Package links work without additional configuration. Use Command-click on macOS or Control-click on Linux and Windows.

Version hints

Zed disables inlay hints by default. Enable them in your settings:

{
  "inlay_hints": {
    "enabled": true,
    "show_background": false
  }
}

An installed package is shown as v3.2.1. If an update is available, the hint becomes v3.2.1 → v3.3.0.

Versions are read from vendor/composer/installed.json. If the file is missing or cannot be read, the hint is simply omitted.

Update checks

Update checks are enabled by default and run in the background. Installed versions are displayed immediately; a slow connection, Packagist error, or offline session does not prevent local version hints from appearing.

To disable Packagist requests:

{
  "lsp": {
    "composer-language-server": {
      "initialization_options": {
        "check_updates": false
      }
    }
  }
}

The server checks the newest stable release published on Packagist. It does not resolve Composer constraints or query private repositories, so an update may require a constraint change before Composer can install it.

Neovim

The Neovim integration requires Neovim 0.10 or newer. Install this repository with your plugin manager; no separate LSP framework is needed.

With lazy.nvim:

{
  "BastenIT/zed-composer-support",
}

The first composer.json you open triggers a download of the native server for your operating system and CPU. Automatic installation uses curl. Once attached, gx opens the package under the cursor on Packagist and inlay hints show installed and available versions.

Defaults can be changed in your plugin specification:

{
  "BastenIT/zed-composer-support",
  config = function()
    require("composer_support").setup({
      check_updates = true,
      inlay_hints = true,
      open_key = "gx",
      -- server_path = "/absolute/path/to/composer-language-server",
    })
  end,
}

Set auto_install = false if you manage the binary yourself. Set open_key = false to leave gx untouched. These commands are also available:

• :ComposerSupportInstall downloads the server used by this plugin version.
• :ComposerSupportInfo shows the active server path.
• :ComposerOpenPackage opens the package under the cursor.
• :checkhealth composer_support checks the Neovim version, download tool, and release target.

How it works

The Zed extension is a small WebAssembly launcher written in Rust. It downloads the matching native composer-language-server binary for the current operating system and CPU architecture.

Neovim uses a small Lua adapter to install and launch that same binary. Parsing, Composer metadata handling, caching, version comparison, and Packagist requests all remain in the native Rust process.

The language server reuses parsed documents and unchanged Composer metadata. Network requests are cached, deduplicated, limited to four concurrent requests and capped at 256 requests per hour. Successful lookups are cached for six hours and failed lookups for fifteen minutes.

Packagist results and the request budget are stored in an editor cache directory, so restarting Zed or Neovim does not clear them. Multiple language-server processes coordinate through the same locked cache file. If that file is missing, damaged, or not writable, the server falls back to an in-memory cache without disabling package links or installed-version hints.

Release binaries are provided for Intel and ARM systems on macOS, Linux, and Windows. Linux binaries are statically linked with musl and do not depend on the host distribution's glibc version.

Development

Requirements:

• Rust stable
• The wasm32-wasip2 Rust target
• Neovim 0.10+ to check the Neovim adapter

Build the language server, install the repository as a Zed dev extension, and point Zed at the local binary:

cargo build -p composer-language-server

In Zed, open the Extensions page, choose Install Dev Extension, and select this repository. Then add the local binary to your settings:

{
  "lsp": {
    "composer-language-server": {
      "binary": {
        "path": "/absolute/path/to/zed-composer-support/target/debug/composer-language-server"
      }
    }
  }
}

Restart the Composer language server after rebuilding it.

Run the project checks with:

cargo fmt --all --check
cargo test -p composer-language-server
cargo clippy -p composer-language-server --all-targets -- -D warnings
cargo check -p zed_composer_support --target wasm32-wasip2
nvim --headless -u NONE -l scripts/check-neovim.lua
cargo build -p composer-language-server
nvim --headless -u NONE -l scripts/check-neovim-lsp.lua

See CONTRIBUTING.md for the release checklist.

Development disclosure

AI tools helped with implementation and review. The project is directed and maintained by a human at BastenIT, who chooses the features, tests the extension, reviews changes, and approves releases.

BastenIT

Built and maintained by BastenIT.

License

MIT