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-08-31 03:53:10
IssueManagement Licenses MIT
仓库地址 git+ 用户数 349
Node Engine ^8.10.0 || ^10.13.0 || >=11.10.1 文件大小 552.5 KB
install test lint fuzz generate-release generate-alpharelease generate-betarelease generate-rcrelease publish-release docs gensite webpack perf


[![NPM version][npm-image]][npm-url] [![Build Status](]( [![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. ## Table of Contents 1. [Installation and Usage](#installation-and-usage) 2. [Configuration](#configuration) 3. [Code of Conduct](#code-of-conduct) 4. [Filing Issues](#filing-issues) 5. [Frequently Asked Questions](#faq) 6. [Releases](#releases) 7. [Semantic Versioning Policy](#semantic-versioning-policy) 8. [License](#license) 9. [Team](#team) 10. [Sponsors](#sponsors) 11. [Technology Sponsors](#technology-sponsors) ## Installation and Usage Prerequisites: [Node.js]( (`^8.10.0`, `^10.13.0`, or `>=11.10.1`) built with SSL support. (If you are using an official Node.js distribution, SSL is always built in.) You can install ESLint 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 ``` ## 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? Yes. [JSCS has reached end of life]( and is no longer supported. We have prepared a [migration guide]( to help you convert your JSCS settings to an ESLint configuration. We are now at or near 100% compatibility with JSCS. If you try ESLint and believe we are not yet compatible with a JSCS rule/configuration, please create an issue (mentioning that it is a JSCS compatibility issue) and we will evaluate it as per our normal process. ### 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? * 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. * 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, 2018, and 2019. 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. * `eslint:recommended` is updated and will result in strictly fewer errors (e.g., rule removals). * Major release (likely to break your lint build) * `eslint:recommended` is updated and may result in new errors (e.g., rule additions, most rule option updates). * 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

Kai Cataldo

Teddy Katz
### Reviewers The people who review and implement new features.

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

Gyandeep Singh

Pig Fang

Milos Djermanovic
## 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

Shopify Salesforce Badoo Airbnb Facebook Open Source

Silver Sponsors

AMP Project

Bronze Sponsors

UI UX Design Agencies Top Web Design Agencies Bugsnag Stability Monitoring Crosswordsolver Codacy Mixpanel VPS Server Free Icons by Icons8 EduBirdie clay Discord ThemeIsle TekHattan Marfeel Fire Stick Tricks JSHeroes

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


GroupId ArtifactID Version 引用量
Sebastian McKenzie @babel/code-frame 7.8.3 378
Evgeny Poberezkin ajv 6.12.0 4698
qix chalk 3.0.0 59866
André Cruz cross-spawn 7.0.1 6594
TJ Holowaychuk debug 4.1.1 23374
constellation doctrine 3.0.0 314
eslint eslint-scope 5.0.0 73
Toru Nagashima eslint-utils 2.0.0 131
Toru Nagashima eslint-visitor-keys 1.1.0 43
Nicholas C. Zakas espree 6.1.2 362
Joel Feenstra esquery 1.1.0 137
constellation esutils 2.0.3 258
Roy Riojas file-entry-cache 5.0.0 54
Mikola Lysenko functional-red-black-tree 1.0.1 37
Gulp Team glob-parent 5.1.0 243
Sindre Sorhus globals 12.3.0 240
kael ignore 5.1.4 424
Sindre Sorhus import-fresh 3.2.0 174
Jens Taylor imurmurhash 0.1.4 86
Simon Boudrias inquirer 7.0.4 17766
Jon Schlinkert is-glob 4.0.1 313
Vladimir Zapparov js-yaml 3.13.1 7743
James Halliday json-stable-stringify-without-jsonify 1.0.1 7
George Zahariev levn 0.3.0 46
John-David Dalton lodash 4.17.15 87062
Isaac Z. Schlueter minimatch 3.0.4 3314
isaacs mkdirp 1.0.2 24527
Lauri Rooden natural-compare 1.4.0 41
George Zahariev optionator 0.8.3 238
TJ Holowaychuk progress 2.0.3 1982
Toru Nagashima regexpp 3.0.0 32
adam_baldwin semver 7.1.3 20807
Sindre Sorhus strip-ansi 6.0.0 2716
Sindre Sorhus strip-json-comments 3.0.0 749
Gajus Kuizinas table 5.4.6 403
James Halliday text-table 0.2.0 616
Andres Suarez v8-compile-cache 2.1.0 125


GroupId ArtifactID Version 引用量
Sebastian McKenzie @babel/core 7.8.4 66761
Henry Zhu @babel/preset-env 7.8.4 55667
adrianheine acorn 7.1.0 2416
Luis Couto babel-loader 8.0.6 78433
Jake Luer chai 4.2.0 90846
Matt Mueller cheerio 1.0.0-rc.3 10490
Declan de Wet common-tags 1.8.0 592
Steven Levithan dateformat 3.0.3 1375
Matthew Eernisse ejs 3.0.1 7205
Nicholas C. Zakas eslint 6.8.0 188008
Nicholas C. Zakas eslint-config-eslint 6.0.0 272
Teddy Katz eslint-plugin-eslint-plugin 2.2.1 113
Toru Nagashima eslint-plugin-node 11.0.0 24568
Nicholas C. Zakas eslint-release 1.2.0 25
Simon Lydell eslump 2.0.0 3
Ariya Hidayat esprima 4.0.1 2006
Isaac Z. Schlueter glob 7.1.6 24078
Michael Mathews jsdoc 3.6.3 7775
Vojta Jina karma-chrome-launcher 3.1.0 25250
Vojta Jina karma-mocha 1.3.0 10560
Litixsoft GmbH karma-mocha-reporter 2.2.5 5177
Tobias Koppers @sokra karma-webpack 3.0.5 11520
nzakas leche 2.3.0 54
Andrey Okonetchnikov lint-staged 10.0.7 26731
Gyandeep Singh load-perf 0.2.0 8
David Anson markdownlint 0.19.0 111
Igor Shubovych markdownlint-cli 0.22.0 682
fb metro-memory-fs 0.58.0 62
Michael Allen mocha-junit-reporter 1.23.3 1287
Duncan Wong npm-license 0.3.3 40
Ben Coe nyc 15.0.0 37212
Thorsten Lorenz proxyquire 2.1.3 5239
Ben Newman recast 0.18.6 762
Ben Newman regenerator-runtime 0.13.3 5554
artur shelljs 0.8.2 12221
Bruce Williams temp 0.9.1 1991
bebraw webpack-cli 3.3.11 48245
yyx990803 yorkie 2.0.0 42