JSHint is a static code analysis tool used in software development for checking if JavaScript source code complies with coding rules.[1] JSHint was created in 2011 by Anton Kovalyov as a fork of the JSLint project (by Douglas 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 an online version, and a command-line version.
| Original author(s) | Anton Kovalyov, forked from original code by Douglas Crockford |
|---|---|
| Initial release | February 18, 2011 |
| Stable release | 2.13.6
/ November 12, 2022 |
| Repository | |
| Written in | JavaScript |
| Operating system | Cross-platform |
| Available in | English |
| Type | Static code analysis |
| License | MIT license |
| Website | jshint |
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 a Node.js module), enables automated linting processes by integrating JSHint into a project's development workflow.[9]
License
editUntil 2020, JSHint was distributed under the MIT license except for one file which was still under the JSLint 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 the Free Software Foundation, made the software non-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]
See also
editReferences
edit- ^ a b Graham, Wayne (2012). Beginning Facebook Game Apps Development. Apress. ISBN 9781430241706.[permanent dead link]
- ^ "Why I forked JSLint to JSHint". anton.kovalyov.net. Anton Kovalyov. 2011-02-20. Archived from the original on 2011-02-24. Retrieved 2018-02-26.
[JSLint] has gotten uncomfortably opinionated
- ^ "JSHint: A Community Driven Fork of JSLint". badassjs.com. Devon Govett. 18 February 2011. Archived from the original on 21 February 2011. Retrieved 2011-02-21.
[..] JSLint was getting a bit too opinionated [..]
- ^ Elliot, Ian (21 February 2011). "JSHint - the (gentler) JavaScript code quality tool". www.i-programmer.info. Archived from the original on 2011-02-23. Retrieved 2018-02-26.
- ^ "Paren-Free". Brendan Eich. 2011-02-28. Archived from the original on 2011-02-28. Retrieved 2018-02-26.
- ^ "Help: JSHint". codekitapp.com. 2018-02-26. Retrieved 2018-02-26.
designed to be less opinionated and more configurable
- ^ "JSLint vs JSHint". Scott Logic. Retrieved 2018-02-26.
- ^ "JSHint Team on GitHub". GitHub. Retrieved 2018-02-26.
Anton Kovalyov, Paul Irish, Rick Waldron, Mike Pennisi (@jugglinmike)
- ^ Kovalyov, Anton. "JSHint - a JavaScript Code Quality Tool". Retrieved 22 January 2013.
- ^ https://www.gnu.org/licenses/license-list.en.html#JSON see the comment about the JSON license
- ^ "You May Finally Use JSHint for Evil". mikepennisi.com. 2020-08-03. Retrieved 2020-08-03.
Further reading
edit- Zakas, Nicholas (May 2012). Maintainable JavaScript (1 ed.). O'Reilly Media. ISBN 978-1-449-32768-2.
- Otero, Cesar (May 2012). Professional jQuery (1 ed.). John Wiley & Sons. ISBN 978-1-118-02668-7.
- Ullman, Larry (February 2012). Modern JavaScript: Develop and Design (1 ed.). Peachpit Press. ISBN 978-0321812520.
- "JSHint - the (gentler) JavaScript code quality tool". IProgrammer. February 21, 2011. Retrieved June 6, 2012.