+0
日增长
9,080
stars
1,619
forks
283
watchers
1,221
prs
2,431
issues
50
releases
README
JSHint, A Static Code Analysis Tool for JavaScript \ [Use it online • Docs • FAQ • Install • Contribute • Blog • Twitter \] JSHint is a community-driven tool that detects errors and potential problems in JavaScript code. Since JSHint is so flexible, you can easily adjust it in the environment you expect your code to execute. JSHint is publicly available and will always stay this way. Our goal The project aims to help JavaScript developers write complex programs without worrying about typos and language gotchas. Any code base eventually becomes huge at some point, so simple mistakes — that would not show themselves when written — can become show stoppers and add extra hours of debugging. So, static code analysis tools come into play and help developers spot such problems. JSHint scans a program written in JavaScript and reports about commonly made mistakes and potential bugs. The potential problem could be a syntax error, a bug due to an implicit type conversion, a leaking variable, or something else entirely. Only 15% of all programs linted on jshint.com pass the JSHint checks. In all other cases, JSHint finds some red flags that could've been bugs or potential problems. Please note, that while static code analysis tools can spot many different kind of mistakes, it can't detect if your program is correct, fast or has memory leaks. You should always combine tools like JSHint with unit and functional tests as well as with code reviews. Reporting a bug To report a bug simply create a new GitHub Issue and describe your problem or suggestion. We welcome all kinds of feedback regarding JSHint including but not limited to: When JSHint doesn't work as expected When JSHint complains about valid JavaScript code that works in all browsers When you simply want a new option or feature Before reporting a bug, please look around to see if there are any open or closed tickets that discuss your issue, and remember the wisdom: pull request bug report tweet. Who uses JSHint? Engineers from these companies and projects use JSHint: Mozilla Wikipedia Facebook Twitter Disqus Medium Yahoo! SmugMug jQuery UI (Source) jQuery Mobile (Source) Coursera RedHat SoundCloud Nodejitsu Yelp Find My Electric Voxer EnyoJS QuickenLoans Cloud9 CodeClimate Zendesk Google Codacy ref Spotify And many more! License JSHint is licensed under the MIT Expat license. Prior to version 2.12.0 (release in August 2020), JSHint was partially licensed under the non-free JSON license. The 2020 Relicensing document details the process maintainers followed to change the license. The JSHint Team JSHint is currently maintained by Rick Waldron, Caitlin Potter, Mike Pennisi, and Luke Page. You can reach them via [email protected]. Previous Maintainers Originating from the JSLint project in 2010, JSHint has been maintained by a number of dedicated individuals. In chronological order, they are: Douglas Crockford, Anton Kovalyov, and Mike Sher
Top issues
#3151Tab indentation breaks multiple rules29 comments · 2017-06-23#2601Add support for experimental configuration29 comments · 2015-07-30#2308Rhino fails on [email protected]24 comments · 2015-04-13#2297Please add support for ES7 method decorators21 comments · 2015-04-11#1487Double NOT operator in IF statement's expression20 comments · 2014-01-24#833Look for .jshintrc's in the directory being linted?20 comments · 2013-01-25#3447Feature Request: Support for top-level await19 comments · 2020-02-05#2904Regular parameters should not come after default parameters19 comments · 2016-03-31
Latest release
JSHint 2.13.6 2.13.6 2022-11-112.13.6 (2022-11-11) Bug Fixes Allow initializing const bindings to undef (fedaf6f) Correct error message (03b1a06)