Need help with esprint?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

608 Stars 43 Forks Apache License 2.0 140 Commits 15 Opened issues


Fast eslint runner

Services available


Need anything else?

Contributors list

esprint - a fast eslint runner GitHub Workflow Status npm version

esprint (pronounced E-S-sprint) speeds up eslint by running the linting engine across multiple threads. esprint sets up a server daemon to cache the lint status of each file in memory. It uses a watcher to determine when files change, to only lint files as necessary. It also has a CI mode where it does not set up a daemon and just lints in parallel.


In order to use esprint, first place an

file in the root directory your project. This is similar to a
if you use flow types. The
file describes which paths to lint and which paths to ignore. You can also override the port to start the background server on. A sample
  "paths": ["foo/*.js", "bar/**/*.js"],
  "ignored": ["**/node_modules/**/*"],
  "port": 5004


| Name | Type | Description | | :---------------: | :---------------: | :---------------------------------------------------------------------------------------------------------------- | |


| Glob-style paths for files to include when linting | |
| Glob-style paths to ignore (not watch) during dev mode for better performance (
applies as normal) | |
| (optional) Run the esprint background server on a specific port | |
| (optional) Use a specific output format - default: stylish | |
| (optional) Report errors only - default: false | |
| (optional) The max number of warnings that should trigger a failure. The default is to not fail on warnings |


Default mode

To run esprint, use the following command anywhere in your project:


esprint will find the root of your project automatically and lint the whole project. In default mode, esprint will start a background server to watch source files and cache lint results in memory.

By default, esprint will split up linting duties across all CPUs in your machine. You can manually override this via the cli with the following argument:

esprint --workers=[num_workers]

To kill the esprint server in the background & clear the cache, use the following command:

esprint stop

You can run

from any subdirectory that
is located in, and it will still properly lint all files as specified.

CI Mode

In CI environments, it is not always appropriate (or necessary) to start a background server. In this case, you can use the following command, which simply lints in parallel without setting up a background server:

esprint check

CLI Options

Auto fix

To use the eslint auto fix feature, add

when starting the server
esprint --fix

or when running in CI mode

esprint check --fix


Print debug output for esprint. Should only be used when you're running into issues

esprint --esprintDebug

Disable watchman

esprint --noWatchman

Developing for esprint


We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.