An AST-based pattern checker for JavaScript.
ast lint javascript ecmascript espree


Project Name eslint Project Url
InceptionYear 2013-07-04 17:01:31 更新时间 2019-02-19 01:16:01
IssueManagement Licenses MIT
仓库地址 git+ 用户数 345
Node Engine ^6.14.0 || ^8.10.0 || >=9.10.0 文件大小 519.3 KB
install test lint fuzz generate-release generate-alpharelease generate-betarelease generate-rcrelease publish-release docs gensite browserify perf profile coveralls


[![NPM version][npm-image]][npm-url] [![build status][travis-image]][travis-url] [![Build status][appveyor-image]][appveyor-url] [![Downloads][downloads-image]][downloads-url] [![Bountysource](]( [![Join the chat at](]( [![FOSSA Status](]( # ESLint [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. ## Configuration After running `eslint --init`, you'll have a `.eslintrc` file in your directory. In it, you'll see some rules configured like this: ```json { "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: * [Bug Report]( * [Propose a New Rule]( * [Proposing a Rule Change]( * [Request a Change]( ## 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](#installation-and-usage). 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]( ## Releases 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. ## License [![FOSSA Status](]( ## Team 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
### Committers The people who review and fix bugs and help triage issues.


Pig Fang
## Sponsors 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

Facebook Open Source Airbnb

Silver Sponsors

AMP Project

Bronze Sponsors


## Technology Sponsors * Site search ([]( is sponsored by [Algolia]( [npm-image]: [npm-url]: [travis-image]: [travis-url]: [appveyor-image]: [appveyor-url]: [coveralls-image]: [coveralls-url]: [downloads-image]: [downloads-url]:


GroupId ArtifactID Version 引用量
Sebastian McKenzie @babel/code-frame 7.0.0 7
Evgeny Poberezkin ajv 6.9.0 2872
qix chalk 2.4.2 42634
André Cruz cross-spawn 6.0.5 4367
TJ Holowaychuk debug 4.1.1 23374
constellation doctrine 3.0.0 314
eslint eslint-scope 4.0.0 13
Toru Nagashima eslint-utils 1.3.1 4
Toru Nagashima eslint-visitor-keys 1.0.0 12
Nicholas C. Zakas espree 5.0.1 297
Joel Feenstra esquery 1.0.1 85
constellation esutils 2.0.2 193
Roy Riojas file-entry-cache 5.0.0 54
Mikola Lysenko functional-red-black-tree 1.0.1 37
Isaac Z. Schlueter glob 7.1.3 17962
Sindre Sorhus globals 11.11.0 164
kael ignore 5.0.5 349
Sindre Sorhus import-fresh 3.0.0 86
Jens Taylor imurmurhash 0.1.4 86
Simon Boudrias inquirer 6.2.2 10805
Vladimir Zapparov js-yaml 3.12.1 7037
James Halliday json-stable-stringify-without-jsonify 1.0.1 7
George Zahariev levn 0.3.0 46
John-David Dalton lodash 4.17.11 874
Isaac Z. Schlueter minimatch 3.0.4 3314
James Halliday mkdirp 0.5.1 18983
Lauri Rooden natural-compare 1.4.0 41
George Zahariev optionator 0.8.2 162
Domenic Denicola path-is-inside 1.0.2 135
TJ Holowaychuk progress 2.0.3 1982
Toru Nagashima regexpp 2.0.1 8
isaacs semver 5.6.0 12022
Sindre Sorhus strip-ansi 5.0.0 1726
Sindre Sorhus strip-json-comments 2.0.1 605
Gajus Kuizinas table 5.2.3 300
James Halliday text-table 0.2.0 616


GroupId ArtifactID Version 引用量
Sebastian McKenzie @babel/core 7.3.3 23037
Sebastian McKenzie @babel/polyfill 7.2.5 2238
Henry Zhu @babel/preset-env 7.3.0 16136
Sebastian McKenzie babelify 10.0.0 8661
Chris Dickinson beefy 2.1.8 462
James Halliday brfs 2.0.2 2053
Jake Luer chai 4.2.0 90846
Matt Mueller cheerio 1.0.0-rc.2 9096
Declan de Wet common-tags 1.8.0 592
Gregg Caines coveralls 3.0.2 354
Steven Levithan dateformat 3.0.3 1375
Matthew Eernisse ejs 2.6.1 5329
Teddy Katz eslint-plugin-eslint-plugin 2.0.1 50
Toru Nagashima eslint-plugin-node 8.0.1 14045
Teddy Katz eslint-plugin-rulesdir 0.1.0 10
Nicholas C. Zakas eslint-release 1.2.0 25
Teddy Katz eslint-rule-composer 0.3.0 4
Simon Lydell eslump 2.0.0 3
Ariya Hidayat esprima 4.0.1 2006
Krishnan Anantheswaran istanbul 0.4.5 223
Michael Mathews jsdoc 3.5.5 6026
Shuhei Kagawa karma-babel-preprocessor 8.0.0 1750
Vojta Jina karma-chrome-launcher 2.2.0 19201
Vojta Jina karma-mocha 1.3.0 10560
Litixsoft GmbH karma-mocha-reporter 2.2.5 5177
nzakas leche 2.2.3 51
Gyandeep Singh load-perf 0.2.0 8
David Anson markdownlint 0.12.0 72
Tim Schaub mock-fs 4.8.0 1248
Duncan Wong npm-license 0.3.3 40
Thorsten Lorenz proxyquire 2.1.0 4361
artur shelljs 0.8.2 12221
Bruce Williams temp 0.9.0 1790
Dominic Tarr through 2.3.8 2706