Skip to content
A fully pluggable tool for identifying and reporting on patterns in JavaScript
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Docs: Ensure `triage` label is added to new issues (#11182) Dec 12, 2018
bin Fix: Remove duplicate error message on crash (fixes #8964) (#10865) Sep 20, 2018
conf Chore: avoid hard-coding the list of core rules in eslint:recommended ( Jan 30, 2019
docs Docs: fix duplicate punctuation in CLI docs (#11528) Mar 19, 2019
messages Fix: Update all-files-ignored.txt message to be less confusing (#11075) Dec 8, 2018
packages/eslint-config-eslint Chore: eslint-config-eslint enable comma-dangle functions: "never" (#… Mar 6, 2019
templates Upgrade: eslint-release@1.2.0 (#11073) Nov 10, 2018
tests Fix: avoid moving comments in implicit-arrow-linebreak (fixes #11521) ( Mar 18, 2019
tools Chore: use "file:" dependencies for internal rules/config (#11465) Mar 6, 2019
.codeclimate.yml Build: Enable CodeClimate (fixes #4068) Oct 6, 2015
.eslintignore New: add no-misleading-character-class (fixes #10049) (#10511) Jul 30, 2018
.eslintrc.js Chore: make test-case-property-ordering reasonable (#11511) Mar 15, 2019
.gitattributes Fix: ignored-paths for Windows path (fixes #10687) (#10691) Aug 2, 2018
.gitignore Upgrade: eslint-release@1.0.0 (refs #10631) (#10991) Oct 19, 2018
.npmrc Chore: Prevent package-lock.json files from being created (fixes #8742)… Jun 16, 2017
.travis.yml Build: update CI testing configuration (#11500) Mar 13, 2019 Build: changelog update for 5.15.3 Mar 18, 2019 Docs: Increase visibility of code of conduct (fixes #8758) (#8764) Jun 19, 2017
LICENSE Docs: Remove extra header line from LICENSE (#8448) Apr 11, 2017
Makefile.js Build: compile deps to ES5 when generating browser file (fixes #11504) ( Mar 15, 2019 Sponsors: Sync README with website Mar 7, 2019 Docs: Create (#9031) Jul 31, 2017
appveyor.yml Build: use Node 8 in appveyor (#9595) Nov 8, 2017
karma.conf.js Chore: lint all files in the repo at the same time (#11425) Feb 21, 2019
package.json 5.15.3 Mar 18, 2019
webpack.config.js Build: compile deps to ES5 when generating browser file (fixes #11504) ( Mar 15, 2019

NPM version build status Build status Downloads Bountysource Join the chat at FOSSA Status


Website | Configuring | Rules | Contributing | Reporting Bugs | Code of Conduct | Twitter | Mailing List | Chat Room

ESLint is a tool for identifying and reporting on patterns found in ECMAScript/JavaScript code. In many ways, it is similar to JSLint and JSHint with a few exceptions:

  • ESLint uses Espree for JavaScript parsing.
  • ESLint uses an AST to evaluate patterns in code.
  • ESLint is completely pluggable, every single rule is a plugin and you can add more at runtime.

Installation and Usage

Prerequisites: Node.js (>=6.14), npm version 3+.

There are two ways to install ESLint: globally and locally.

Local Installation and Usage

If you want to include ESLint as part of your project's build system, we recommend installing it locally. You can do so using npm:

$ npm install eslint --save-dev

You should then set up a configuration file:

$ ./node_modules/.bin/eslint --init

After that, you can run ESLint on any file or directory like this:

$ ./node_modules/.bin/eslint yourfile.js

Any plugins or shareable configs that you use must also be installed locally to work with a locally-installed ESLint.

Global Installation and Usage

If you want to make ESLint available to tools that run across all of your projects, we recommend installing ESLint globally. You can do so using npm:

$ npm install -g eslint

You should then set up a configuration file:

$ eslint --init

After that, you can run ESLint on any file or directory like this:

$ eslint yourfile.js

Any plugins or shareable configs that you use must also be installed globally to work with a globally-installed ESLint.

Note: eslint --init is intended for setting up and configuring ESLint on a per-project basis and will perform a local installation of ESLint and its plugins in the directory in which it is run. If you prefer using a global installation of ESLint, any plugins used in your configuration must also be installed globally.


After running eslint --init, you'll have a .eslintrc file in your directory. In it, you'll see some rules configured like this:

    "rules": {
        "semi": ["error", "always"],
        "quotes": ["error", "double"]

The names "semi" and "quotes" are the names of rules in ESLint. The first value is the error level of the rule and can be one of these values:

  • "off" or 0 - turn the rule off
  • "warn" or 1 - turn the rule on as a warning (doesn't affect exit code)
  • "error" or 2 - turn the rule on as an error (exit code will be 1)

The three error levels allow you fine-grained control over how ESLint applies rules (for more configuration options and details, see the configuration docs).

Code of Conduct

ESLint adheres to the JS Foundation Code of Conduct.

Filing Issues

Before filing an issue, please be sure to read the guidelines for what you're reporting:

Frequently Asked Questions

I'm using JSCS, should I migrate to ESLint?

Maybe, depending on how much you need it. JSCS has reached end of life, but if it is working for you then there is no reason to move yet. There are still a few issues pending. We’ll announce when all of the changes necessary to support JSCS users in ESLint are complete and will start encouraging JSCS users to switch to ESLint at that time.

If you are having issues with JSCS, you can try to move to ESLint. Have a look at our migration guide.

Does Prettier replace ESLint?

No, ESLint does both traditional linting (looking for problematic patterns) and style checking (enforcement of conventions). You can use ESLint for everything, or you can combine both using Prettier to format your code and ESLint to catch possible errors.

Why can't ESLint find my plugins?

ESLint can be globally or locally installed. If you install ESLint globally, your plugins must also be installed globally; if you install ESLint locally, your plugins must also be installed locally.

If you are trying to run globally, make sure your plugins are installed globally (use npm ls -g).

If you are trying to run locally:

  • Make sure your plugins (and ESLint) are both in your project's package.json as devDependencies (or dependencies, if your project uses ESLint at runtime).
  • Make sure you have run npm install and all your dependencies are installed.

In all cases, make sure your plugins' peerDependencies have been installed as well. You can use npm view eslint-plugin-myplugin peerDependencies to see what peer dependencies eslint-plugin-myplugin has.

Does ESLint support JSX?

Yes, ESLint natively supports parsing JSX syntax (this must be enabled in configuration). Please note that supporting JSX syntax is not the same as supporting React. React applies specific semantics to JSX syntax that ESLint doesn't recognize. We recommend using eslint-plugin-react if you are using React and want React semantics.

What ECMAScript versions does ESLint support?

ESLint has full support for ECMAScript 3, 5 (default), 2015, 2016, 2017, and 2018. You can set your desired ECMAScript syntax (and other settings, like global variables or your target environments) through configuration.

What about experimental features?

ESLint's parser only officially supports the latest final ECMAScript standard. We will make changes to core rules in order to avoid crashes on stage 3 ECMAScript syntax proposals (as long as they are implemented using the correct experimental ESTree syntax). We may make changes to core rules to better work with language extensions (such as JSX, Flow, and TypeScript) on a case-by-case basis.

In other cases (including if rules need to warn on more or fewer cases due to new syntax, rather than just not crashing), we recommend you use other parsers and/or rule plugins. If you are using Babel, you can use the babel-eslint parser and eslint-plugin-babel to use any option available in Babel.

Once a language feature has been adopted into the ECMAScript standard (stage 4 according to the TC39 process), we will accept issues and pull requests related to the new feature, subject to our contributing guidelines. Until then, please use the appropriate parser and plugin(s) for your experimental feature.

Where to ask for help?

Join our Mailing List or Chatroom.


We have scheduled releases every two weeks on Friday or Saturday. You can follow a release issue for updates about the scheduling of any particular release.

Semantic Versioning Policy

ESLint follows semantic versioning. However, due to the nature of ESLint as a code quality tool, it's not always clear when a minor or major version bump occurs. To help clarify this for everyone, we've defined the following semantic versioning policy for ESLint:

  • Patch release (intended to not break your lint build)
    • A bug fix in a rule that results in ESLint reporting fewer errors.
    • A bug fix to the CLI or core (including formatters).
    • Improvements to documentation.
    • Non-user-facing changes such as refactoring code, adding, deleting, or modifying tests, and increasing test coverage.
    • Re-releasing after a failed release (i.e., publishing a release that doesn't work for anyone).
  • Minor release (might break your lint build)
    • A bug fix in a rule that results in ESLint reporting more errors.
    • A new rule is created.
    • A new option to an existing rule that does not result in ESLint reporting more errors by default.
    • An existing rule is deprecated.
    • A new CLI capability is created.
    • New capabilities to the public API are added (new classes, new methods, new arguments to existing methods, etc.).
    • A new formatter is created.
  • Major release (likely to break your lint build)
    • eslint:recommended is updated.
    • A new option to an existing rule that results in ESLint reporting more errors by default.
    • An existing formatter is removed.
    • Part of the public API is removed or changed in an incompatible way.

According to our policy, any minor update may report more errors than the previous release (ex: from a bug fix). As such, we recommend using the tilde (~) in package.json e.g. "eslint": "~3.1.0" to guarantee the results of your builds.


FOSSA Status


These folks keep the project moving and are resources for help.

Technical Steering Committee (TSC)

The people who manage releases, review feature requests, and meet regularly to ensure ESLint is properly maintained.

Nicholas C. Zakas

Kevin Partington

Ilya Volodin

Brandon Mills

Toru Nagashima

Gyandeep Singh

Kai Cataldo

Teddy Katz


The people who review and fix bugs and help triage issues.


Pig Fang


The following companies, organizations, and individuals support ESLint's ongoing maintenance and development. Become a Sponsor to get your logo on our README and website.

Gold Sponsors

Airbnb Facebook Open Source Badoo

Silver Sponsors

AMP Project

Bronze Sponsors

Faithlife JSHeroes

Technology Sponsors

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.