elixir-lsp/elixir-ls

This system is an Elixir Language Server (ElixirLS) that provides IDE features such as auto-completion, hover documentation, and code navigation. It implements the Language Server Protocol (LSP) and Debug Adapter Protocol (DAP) to support editing, debugging, and static analysis. The server integrates with Ecto and Phoenix frameworks and includes an embedded Model Context Protocol (MCP) server for LLM-based code analysis.

This period focused on modernizing the ElixirLS codebase by removing legacy debugger and I/O handler components in favor of a streamlined, standalone language server architecture. The update introduced incremental Dialyzer analysis, native type inference, and new LSP features like call hierarchy and code actions, supported by comprehensive test coverage for the refactored utilities.

21 changes

This period focused on significantly expanding the language server's capabilities by adding new features such as code lenses for test execution, LLM-optimized commands, and code folding support. Concurrently, the team invested heavily in test coverage, introducing comprehensive tests and fixtures for these new features and core analysis providers to ensure stability and correctness across different environments.

21 changes

This period focused on significantly expanding the language server's capabilities by introducing new providers for code actions, implementation resolution, and framework-specific completions for Ecto and Phoenix. Concurrently, the debug adapter was renamed and hardened with version checks, while extensive test suites were added across both components to ensure robustness and fix existing crashes.

30 changes

This period focused on expanding the language server's capabilities by implementing new providers for call hierarchy and callback/protocol declarations. It also introduced comprehensive support for the Debug Adapter Protocol and the Model Context Protocol, alongside extensive test coverage for these new features.

9 changes

elixir-lsp/elixir-ls was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.