Skip to content
/ jshint Public
forked from jshint/jshint

JSHint is a community-driven tool to detect errors in JavaScript code and enforce your team's coding conventions.

License

Notifications You must be signed in to change notification settings

clog/jshint

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

JSHint, A Static Code Analysis Tool for JavaScript

Build Status NPM version

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/.

JSHint Fundraiser / Bug Bounties

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:

  1. All funds (aside from fees) will be used only to fund bounties.
  2. If core team ends up fixing bounty bugs, the reward will be donated to the Electronic Frontier Foundation.
  3. Before marking bugs as fixed, all patches must be reviewed by a core team member.

Thanks!

Reporting a bug

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 JSHint complains about valid JavaScript code that works in all browsers
  • 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.

FAQ

How do I turn off "mixed tabs and spaces" warning?

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.

Contributing

Look for a file named CONTRIBUTING.md in this repository. It contains our contributing guidelines. We also have a mailing list.

License

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.

Attribution

Core Team members:

Maintainer: Anton Kovalyov

Thank you!

We really appreciate all kind of feedback and contributions. Thanks for using and supporting JSHint!

About

JSHint is a community-driven tool to detect errors in JavaScript code and enforce your team's coding conventions.

Resources

License

Stars

Watchers

Forks

Packages

No packages published