| Original author(s) | Anton Kovalyov, forked from original code byDouglas Crockford |
|---|---|
| Initial release | February 18, 2011; 14 years ago (2011-02-18) |
| Stable release | 2.13.6 / November 12, 2022; 2 years ago (2022-11-12) |
| Repository | |
| Written in | JavaScript |
| Operating system | Cross-platform |
| Available in | English |
| Type | Static code analysis |
| License | MIT license |
| Website | jshint |
JSHint is astatic code analysis tool used insoftware development for checking ifJavaScriptsource code complies withcoding rules.[1] JSHint was created in 2011 by Anton Kovalyov as a fork of theJSLint project (byDouglas Crockford).[2][3] Anton and others felt JSLint was getting "too opinionated", and did not allow enough customization options.[4][5][6][7] The JSHint maintainers[8] publish both anonline version, and acommand-line version.
The online version is accessible through the official website in which users can paste code to run the application online.[1] The command-line version of JSHint (distributed as aNode.js module), enables automatedlinting processes by integrating JSHint into a project's development workflow.[9]
Until 2020, JSHint was distributed under the MIT license except for one file which was still under theJSLint License (a slightly modified version of the MIT license). The additional clause specified that the software shall be used "for Good and not Evil". This clause, according to theFree Software Foundation, made the softwarenon-free.[10]
In August 2020, all code under the previous JSLint License was replaced with open-source software, making the software fully free software.[11]
[JSLint] has gotten uncomfortably opinionated
[..] JSLint was getting a bit too opinionated [..]
designed to be less opinionated and more configurable
Anton Kovalyov, Paul Irish, Rick Waldron, Mike Pennisi (@jugglinmike)
| Dialects | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Engines (comparison) | |||||||||
| Frameworks |
| ||||||||
| People |
| ||||||||
| Other | |||||||||
