JSHint is a community-driven tool to detect errors and potential problems in JavaScript code and to enforce your team's coding conventions. We made JSHint very flexible so you can easily adjust it to your particular coding guidelines and the environment you expect your code to execute in.
Our goal is to help JavaScript developers write complex programs without worrying about typos and language gotchas.
We believe that static code analysis programs—as well as other code quality tools—are important and beneficial to the JavaScript community and, thus, should not alienate their users.
For general usage and hacking information, visit our website: http://jshint.com/.
We're running a fundraiser for JSHint! If JSHint helps you in your day-to-day development, please consider donating. All money raised on this page will be used as monetary rewards for fixing JSHint bugs and implementing new features. Our hope is to introduce more developers to JSHint hacking and boost its development.
Rules:
Thanks!
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:
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:
Maintainer: Anton Kovalyov
We really appreciate all kind of feedback and contributions. Thanks for using and supporting JSHint!