For general usage and hacking information, visit our website: http://jshint.com/.
Some bugs are so important to us, we will pay you if you fix them! Go to our page on BountySource to see which bugs have bounties behind them.
Really want to have something fixed but don't have time? You can add your own bounty to any JSHint bug and make it more attractive for potential contributors!
Rule: A bug is considered fixed only after it has been merged into the master branch of the main JSHint repository.
To report a bug simply create a new GitHub Issue and describe your problem or suggestion. We welcome all kind of feedback regarding JSHint including but not limited to:
- When JSHint doesn't work as expected
- When you simply want a new option or feature
Before reporting a bug look around to see if there are any open or closed tickets that cover your issue. And remember the wisdom: pull request > bug report > tweet.
If you're using so-called smart tabs
then we have an option
smarttabs for you. Otherwise, your solution is to
run JSHint with a custom reporter that discards any warnings you don't like.
For example, this example reporter
discards all warnings about mixed tabs and spaces.
Look for a file named
CONTRIBUTING.md in this repository. It contains our
contributing guidelines. We also have
a mailing list.
JSHint is distributed under the MIT License. One file and one file only (src/stable/jshint.js) is distributed under the slightly modified MIT License.
Core Team members:
- Anton Kovalyov (@valueof)
- Wolfgang Kluge (blog)
- Josh Perez (@goatslacker)
- Brent Lintner (@brentlintner)
- Bernard Pratz (@guyzmo)
Maintainer: Anton Kovalyov
We really appreciate all kind of feedback and contributions. Thanks for using and supporting JSHint!