Speed up eslint to accelerate your development workflow
npm install eslint_d
🪄 Speed up eslint to accelerate your development workflow
> Runs [eslint][] in a background process to improve linting time while editing.
> On a MacBook Air M1 with node.js v22.2.0 and eslint v9.8.0:
``bash`
❯ eslint file.js # ~500ms
❯ eslint_d file.js # ~115ms
- Supports all eslint versions from v4 to v9.
- Supports all LTS versions of node.js.
- Automatically starts, stops and restarts the background server.
- Binds to parent process, editor process or exits after IDLE time.
- Falls back to bundled eslint if local eslint is missing.
`bash`
❯ npm i -g eslint_d
- With [ale][]:
`vim`
let $ESLINT_D_PPID = getpid()
let g:ale_javascript_eslint_executable = 'eslint_d'
let g:ale_javascript_eslint_use_global = 1
- With [syntastic][]:
`vim`
let $ESLINT_D_PPID = getpid()
let g:syntastic_javascript_checkers = ['eslint']
let g:syntastic_javascript_eslint_exec = 'eslint_d'
- With [nvim-lint][]
`lua`
vim.env.ESLINT_D_PPID = vim.fn.getpid()
require('lint').linters_by_ft = {
javascript = {'eslint_d'},
typescript = {'eslint_d'},
}
Use [flycheck][] with the javascript-eslint checker:
`elisp`
(setq flycheck-javascript-eslint-executable "eslint_d")
The official [SublimeLinter-eslint][] plugin automatically prefers eslint_d
if it finds one.
You will not gain any performance from this module as these editors already
cache eslint instances for you.
---
If you're using eslint_d in any other editor, please let us know!
eslint_d is a drop-in replacement for eslint. It forwards all arguments toeslint and starts the background server if necessary:
``
eslint_d [options] file.js [file.js] [dir]
All arguments are passed to eslint, except for the following commands:
``
start Start the daemon
stop Stop the daemon
restart Restart the daemon
status Show daemon status, process id and resolved eslint version
--help, -h Show this help
--version, -v Show version number of eslint_d and bundled eslint
--fix-to-stdout Print fixed file to stdout (requires --stdin)
- ESLINT_D_PPID Parent process id to monitor. If the parent process dies, theESLINT_D_IDLE
daemon exits as well. "0" disables monitoring (default), and "auto" monitors
the parent process that started eslint_d.
- Number of minutes of inactivity before the daemon exits.ESLINT_D_PPID
Defaults to "0" if is set, otherwise "15".ESLINT_D_MISS
- How to behave if local eslint is missing. "fallback" uses theESLINT_D_ROOT
bundled eslint (default). "fail" logs an error and exits with code 1.
"ignore" silently exits with code 0.
- Provide specific directory to search for node_modules/eslint.node_modules
Useful in monorepos where might be in a location other than
the project root.
eslint_d has an additional option that eslint does not have,--fix-to-stdout which prints the fixed file to stdout. This allows editors to--stdin
add before save hooks to automatically fix a file prior to saving. It must be
used with .
Add this to your .vimrc to lint the current buffer or visual selection on:
`vimF
" Autofix entire buffer with eslint_d:
nnoremap
" Autofix visual selection with eslint_d:
vnoremap
``
See eslintd-fix
eslint_d starts a background server that runs eslint in a separate process.eslint_d
It communicates with the server over a Unix domain socket. When you run, it forwards all arguments to the server and prints the result. This
is faster because node.js doesn't have to load all the required modules every
time.
By default, eslint_d uses the local eslint package if available. If theeslint
local package is missing, eslint_d falls back to the bundledeslint package. You can change this behavior with the ESLINT_D_MISSeslint
environment variable. To see which package is used, run eslint_d
status.
A .eslint_d file is stored in the resolved eslint installation directory
which stores a security token, the server port and process id, and the hash of
the monitored files. If the file is removed, the server exits.
The server automatically stops after 15 minutes of inactivity. You can change
this with the ESLINT_D_IDLE environment variable. Alternatively, you can bindESLINT_D_PPID
the lifetime of the server to a parent process by setting toeslint_d
"auto" or a specific parent process id. The server will exit when the parent
process dies. Note that "auto" uses the parent process that started ,
which may not be the editor process.
The server is also automatically restarted if one of the following files
changed: package.json, package-lock.json, npm-shrinkwrap.json,yarn.lock, pnpm-lock.yaml.
> Added in v14.2.0.
Pass the --debug flag to eslint_d to enable debug output. Use the DEBUGeslint_d
environment variable to limit debug output to :
`bash`
❯ DEBUG="eslint_d:*"
For server side debug output, restart with --debug in a separate terminal:
`bash`
❯ eslint_d restart --debug # eslint and eslint_d logs
❯ DEBUG="eslint_d:*" eslint_d restart --debug # eslint_d logs only
This will keep the process attached to the terminal and print debug output.
- 14.0.0: eslint 4 - 9, node 18 - 22 (ships with eslint 9) (see [^1])13.0.0
- : eslint 4 - 8, node 12 - 20 (ships with eslint 8)12.0.0
- : eslint 4 - 8, node 12 - 16 (ships with eslint 8)11.0.0
- : eslint 4 - 8, node 12 - 16 (ships with eslint 7)10.0.0
- : eslint 4 - 7, node 10 - 14 (using new ESLint API if available)9.0.0
- : eslint 4 - 7, node 10 - 14 (using CLIEngine API)8.0.0
- : eslint 4 - 6, node 8 - 127.2.0
- : eslint 4 - 5, node 6 - 107.0.0
- : eslint 5.4+, node 6, 8 and 106.0.0
- : eslint 5.0+, node 6+ (eslint dropped node 4)5.0.0
- : eslint 4.0+4.0.0
- : eslint 3.0+, node 4+ (eslint dropped node 0.10 and 0.12)3.0.0
- : eslint 2.2+1.0.0
- , 2.0.0: eslint 1.4+, node 4 (and probably older)
MIT
[License]: https://img.shields.io/npm/l/eslint_d.svg
[eslint]: https://eslint.org
[ale]: https://github.com/dense-analysis/ale
[syntastic]: https://github.com/scrooloose/syntastic
[nvim-lint]: https://github.com/mfussenegger/nvim-lint
[flycheck]: http://www.flycheck.org/
[SublimeLinter-eslint]: https://github.com/SublimeLinter/SublimeLinter-eslint
[^1]: The support for --fix-to-stdout` is only provided with eslint 5 and beyond.