5:29
| Original author(s) | Douglas Crockford |
|---|---|
| Developer(s) | Douglas Crockford |
| Initial release | 2002 |
| Stable release | 2020-09-09
/ September 9, 2020 |
| Repository |  |
| Written in | JavaScript |
| Operating system | Cross-platform |
| Available in | English |
| Type | Static code analysis |
| License | JSLint License |
| Website | jslint |
JSLint is a static code analysis tool used in software development for checking if JavaScript source code complies with coding rules. It is provided primarily as a browser-based web application accessible through the domain jslint.com, but there are also command-line adaptations.[1] It was created in 2002 by Douglas Crockford.[2]
The JSLint license[3] is a derivative of the MIT License.[4] The sole modification is the addition of the line "The Software shall be used for Good, not Evil."
According to the Free Software Foundation, this clause makes the license non-free.[5] The clause has also prevented JSLint-related software from being hosted on Google Code[4] and from being included in the Debian free software package repositories.[6] Because of this restriction, according to Crockford, IBM asked Crockford in 2011 for a license to do evil, such that their customers could use it.[7][8][9]
JSLint is considered by some to be the first JavaScript syntax checker.[10][11] It has since inspired various other tools.
In 2011, Anton Kovalyov created a fork, called JSHint.[12][13][14] The main motivation behind the creation of JSHint was to provide a "less opinionated" and "more configurable" way for developers to analyse code.[15][16][17]
In 2013, Nicholas C. Zakas created ESLint.[11] Both JSLint and JSHint lacked the ability to create additional rules for code quality and coding style. After contributing to JSHint, Zakas decided to create a new linting tool, ESLint, where all rules are configurable, and additional rules can be defined or loaded at run-time.[18] ESLint also supports linting the latest versions of JavaScript, aka ECMAScript 2015 and above.
In 2014, Marat Dulin created JSCS.[19] In 2016, the JSCS Team joined the ESLint project and has since discontinued maintenance of the JSCS tool.[20][21][22]
In 2015, a comparison published by SitePoint, recommended ESLint above JSLint, JSHint and JSCS.[23] In 2016, CodeKit also praised ESLint for "finding more issues", being "far more configurable", and being "the industry standard" for JavaScript syntax checkers.[10]
In 2016, Palantir Technologies created TSLint,[24] which is the TypeScript equivalent for ESLint.[25] It was deprecated in favor of ESLint with a TypeScript integration in 2019.[26]
Copyright 2002 Douglas Crockford. All Rights Reserved Wrrrldwide and Beyond!
I give permission for IBM, its customers, partners, and minions, to use JSLint for evil.
JSLint is the original JavaScript syntax checker.
JSLint was the state of the art in JavaScript linting technology
[JSLint] has gotten uncomfortably opinionated
[..] JSLint was getting a bit too opinionated [..]
designed to be less opinionated and more configurable
JSLint complaint: not configurable enough. JSHint complaint: still not configurable enough [..]
By: Wikipedia.org
Edited: 2021-06-18 12:30:48
Source: Wikipedia.org
