eslint_d mit Homebrew, Nix, pacman installieren

Projektlinks

• Homepage
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• eslint_d

Projektgeschichte

The npm package was first published in 2015, shortly after ESLint 1.0.0, and its upstream README still presents it as a workflow accelerator rather than a replacement linter. It supports multiple ESLint generations and forwards normal ESLint arguments to a background server.

Adoptionsgeschichte

eslint_d found its niche in editor-driven JavaScript development, especially Vim, Neovim, Emacs, and other environments where a linter may be invoked repeatedly for a single buffer. The README documents integrations for editor linting packages and notes that some editors already cache ESLint themselves.

Wie es verwendet wird

Users install `eslint_d`, run it as a drop-in `eslint` replacement, and let it start, stop, or restart the daemon automatically. It can use the local project ESLint package, fall back to a bundled ESLint, report daemon status, and provide an extra `--fix-to-stdout` option for editor save hooks.

Warum Paket-Nerds sich dafür interessieren

Its significance is mostly ergonomic: it is a small package-manager-era workaround for the cost of repeatedly starting a large JavaScript toolchain. Package nerds care because it shows how wrapper commands, local dependency resolution, daemon files, and editor integrations can change perceived tool speed without changing the underlying linter.

Zeitleiste

• 2015: eslint_d first published to npm.
• 2024: v14.2.0 adds documented debug mode.
• 2026: v15.x line supports modern ESLint and Node.js versions.

Related projects

• eslint_d is directly tied to ESLint and overlaps in use with editor integrations that cache ESLint processes internally.

Quellen

• https://github.com/mantoni/eslint_d.js
• https://www.npmjs.com/package/eslint_d
• https://formulae.brew.sh/formula/eslint_d