ESLint
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "ESLint" – news · newspapers · books · scholar · JSTOR Timestamp: 20190705183030 18:30, 5 July 2019 (UTC) Administrators: delete |
| Original author(s) | Nicholas C. Zakas |
|---|---|
| Developer(s) | Nicholas C. Zakas |
| Initial release | 2013 |
| Stable release | 6.0.1
/ June 15, 2019 |
| Repository | |
| Written in | JavaScript |
| Operating system | Cross-platform |
| Available in | English |
| Type | Static code analysis |
| License | MIT License |
| Website | eslint |
ESLint is a static code analysis tool for identifying problematic patterns found in JavaScript code. It is created by Nicholas C. Zakas in 2013. [1] Rules in ESLint are configurable, and customized rules can be defined and loaded. ESLint covers both code quality and coding style issues. ESLint supports newest standards of ECMAScript, and variant syntax, like experimental syntax, JSX, TypeScript, etc, can also be linted when appropriate parser is configured.