Install vscode-langservers-extracted with Homebrew, Nix, pacman

Project links

• Homepage
• Upstream docs
• Package manager page

Commands and aliases

• vscode-css-language-server
• vscode-eslint-language-server
• vscode-html-language-server
• vscode-json-language-server
• vscode-markdown-language-server

Project history

The repository was created in November 2020 and the npm package was published days later. Its README states the reason plainly: Microsoft had provided useful language servers for the community, but the older standalone packages had not been updated for a long time, so this package extracted newer servers from VS Code.

The project follows the Language Server Protocol model: one language server communicates with many editors over a standard protocol. Microsoft's LSP documentation explains that this avoids reimplementing completion, go-to-definition, hover, and reference features separately for each editor.

The package's `package.json` exposes executables named `vscode-css-language-server`, `vscode-eslint-language-server`, `vscode-html-language-server`, `vscode-json-language-server`, and `vscode-markdown-language-server`. Its README also records third-party licensing links back to Microsoft/vscode, Microsoft/vscode-eslint, and Microsoft/vscode-anycode.

Adoption history

The package became especially visible in Vim, Neovim, Emacs, Helix, Zed, and other LSP-client communities because it reduced setup friction: users could install one npm package and point their editor's LSP client at familiar VS Code language servers.

Repository metadata shows hundreds of GitHub stars, while package metadata and downstream package-manager entries show that it moved beyond npm into system package ecosystems. That adoption pattern is typical of editor-language-server tooling: the upstream package provides the binaries, and editor/plugin maintainers document how to wire them into each client.

How it is used

Users install the package globally or through a system package, then configure an editor LSP client to launch one of the provided executables for CSS, HTML, JSON, ESLint, or Markdown files. The tool itself is not an editor UI; it supplies server processes that speak LSP over stdio or a similar transport expected by the client.

For package users, this formula is convenient because it puts multiple Microsoft-derived language servers on PATH under stable command names, making editor configuration and CI/dev-environment setup simpler.

Why package nerds care

This is a classic package-ecosystem bridge: it unbundles language intelligence from VS Code and makes it consumable by other editors. Its importance is not originality of the language servers, but the packaging work that keeps those servers available as ordinary command-line binaries.

Timeline

• 2020: GitHub repository and npm package are created to provide newer extracted VS Code language servers.
• 2021-2024: Releases continue through the 4.x series, with v4.10.0 published in May 2024.
• 2024: The package metadata lists Markdown alongside CSS, ESLint, HTML, and JSON server executables.

Related projects

• The package is related to Microsoft/vscode, vscode-html-languageserver-bin, vscode-css-langserver-bin, vscode-json-languageserver, vscode-eslint, vscode-anycode, the Language Server Protocol, and editor LSP clients such as Neovim's built-in LSP.

Sources

• GitHub README: https://github.com/hrsh7th/vscode-langservers-extracted
• GitHub repository API metadata: https://api.github.com/repos/hrsh7th/vscode-langservers-extracted
• Microsoft Language Server Protocol overview: https://microsoft.github.io/language-server-protocol/
• npm registry metadata: https://registry.npmjs.org/vscode-langservers-extracted
• package.json: https://raw.githubusercontent.com/hrsh7th/vscode-langservers-extracted/master/package.json