Install yaml-language-server with Homebrew, apk, Nix, pacman

Project links

• Homepage
• Upstream docs
• Package manager page

Commands and aliases

• yaml-language-server

Project history

The GitHub repository was created in July 2017. Red Hat's October 2017 launch article says the work began around Kubernetes syntax support, then broadened into a general YAML language server with built-in Kubernetes support as the team saw a wider opportunity.

The server was published as an npm package in September 2017 and used by Red Hat's VS Code YAML extension, Eclipse Che, and other editor integrations. The README later records major parser and schema support evolution: JSON Schema drafts 04, 07, 2019-09, and 2020-12, and the 1.0.0 switch to the `eemeli/yaml` parser with strict YAML version handling.

Adoption history

Adoption followed the Language Server Protocol pattern: one server package could power multiple editors instead of each editor maintaining its own YAML intelligence. Red Hat's VS Code Marketplace listing describes the extension as YAML support via yaml-language-server with built-in Kubernetes syntax support, and shows a large installed base for the extension.

The server became especially valuable as YAML became the configuration language for Kubernetes, CI systems, Compose files, package metadata, and infrastructure tools. Schema association through JSON Schema Store let the same server understand many file types without hard-coding every ecosystem.

How it is used

Package users normally install the `yaml-language-server` executable and let an editor client launch it over stdio or another LSP transport. Configuration maps schemas to glob patterns, toggles validation, hover, completion, formatting, SchemaStore, Kubernetes CRD discovery, custom YAML tags, key ordering, and YAML 1.1 versus 1.2 parsing behavior.

Its practical value is editor feedback before a YAML file reaches a cluster, CI runner, package tool, or deployment system: bad structure, unknown keys, type errors, and schema mismatches become diagnostics and completions during editing.

Why package nerds care

YAML Language Server is package-nerd glue for the LSP era. It turns a messy, indentation-sensitive data language into reusable editor infrastructure, and its Homebrew/npm-style CLI package matters because editors, terminals, and non-VS Code clients can all share the same server.

Timeline

• 2017-07: The public GitHub repository was created.
• 2017-09: npm records the first `yaml-language-server` package publication.
• 2017-10: Red Hat announced the YAML Language Server and VS Code extension, noting npm availability, Eclipse Che integration, and early reuse by Atom's ide-yaml package.
• 2021: npm records the 1.0.0 release; the README says 1.0.0 switched to the `eemeli/yaml` parser.
• 2020s: The README documents JSON Schema draft 04, 07, 2019-09, and 2020-12 support plus SchemaStore and Kubernetes CRD integration.

Related projects

• vscode-yaml is Red Hat's VS Code extension that uses yaml-language-server.
• JSON Schema Store provides many schemas consumed through the server's schema-store integration.
• eemeli/yaml is the YAML parser used by the server starting with the 1.0.0 line.

Sources

• https://api.github.com/repos/redhat-developer/yaml-language-server
• https://developers.redhat.com/blog/2017/10/18/yaml-language-server-extension-vs-code
• https://github.com/redhat-developer/yaml-language-server#readme
• https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml
• https://registry.npmjs.org/yaml-language-server