Installer bash-language-server avec Homebrew, MacPorts, Nix, pacman

Liens du projet

• Page d'accueil
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• bash-language-server

Historique du projet

The official README describes Bash Language Server as bringing an IDE-like experience for Bash scripts to most editors. It is based on the Tree-sitter Bash parser and integrates with explainshell, ShellCheck, and shfmt.

The project is written for editor integration rather than direct end-user scripting. Its releases are split across server and VS Code client tags, and the README documents installing the server binary from npm or distribution packages for editors that already have generic LSP clients.

Historique d'adoption

Its adoption follows the spread of LSP support from VS Code into Vim, Neovim, Emacs, Sublime Text, Helix, Eclipse, JupyterLab, and other editors. The official README lists clients for all of those editor families, which is the project's real adoption story: one server reused by many editor integrations.

The batch input shows Homebrew, MacPorts, Nix, and Arch packaging. That packaging matters because shell scripting is often edited outside Node-centric workflows, so system package managers make the server available to users who only need the `bash-language-server` executable.

Modes d'utilisation

Users install `bash-language-server`, configure an editor LSP client to run `bash-language-server start`, and optionally install ShellCheck for diagnostics and shfmt for formatting. The README includes editor-specific setup snippets for Vim, Neovim, coc.nvim, ALE, Emacs lsp-mode, Emacs eglot, and other clients.

Configuration is mainly editor/workspace configuration plus environment variables such as `BASH_IDE_LOG_LEVEL`; the README points detailed configuration variables to the project's `config.ts` source.

Pourquoi les passionnés de paquets s'y intéressent

Bash Language Server is package-nerd interesting because it makes shell tooling look like the rest of the LSP era. Instead of each editor shipping its own Bash intelligence, package managers can distribute one server that composes Tree-sitter parsing, ShellCheck linting, shfmt formatting, and editor-native LSP clients.

It is also a reminder that even mature Unix scripting ecosystems keep absorbing new developer-tool protocols. The package is small, but it connects Bash to modern editor workflows without replacing Bash itself.

Chronologie

• 2010s: Language Server Protocol adoption makes reusable editor backends common outside VS Code.
• 2010s: Bash Language Server appears with separate server and VS Code client release tags.
• 2020s: README documents broad editor support including Vim, Neovim, Emacs, Sublime Text, Helix, Eclipse, and JupyterLab.
• 2020s: Homebrew, MacPorts, Nix, and Arch package the server executable.

Related projects

• The official README names Tree-sitter Bash, explainshell, ShellCheck, and shfmt as the main related projects. It also relates the server to editor LSP clients such as Bash IDE for VS Code, vim-lsp, nvim-lspconfig, coc.nvim, ALE, lsp-mode, and eglot.

Sources

• Official GitHub releases page exposes server and VS Code client release streams.
• Official README describes the LSP purpose, Tree-sitter basis, ShellCheck and shfmt integrations, installation, clients, and logging.
• Official config.ts is cited by the README for configuration variables.
• input.source_facts.package-manager lists Homebrew, MacPorts, Nix, and Arch packaging.