JSHint是一个在JavaScript编写的程序中标记可疑用法的程序。 核心项目包括一个库本身以及作为Node模块分发的CLI程序。
JSHint是一个社区驱动的工具,用于检测JavaScript代码中的错误和潜在问题。由于JSHint非常灵活,您可以在期望执行代码的环境中轻松调整它。 JSHint是开源的,永远都是这样。
JSHint是一个帮助您检测JavaScript代码中的错误和潜在问题的工具。(JSHint is a tool that helps to detect errors and potential problems in your JavaScript code.)
JSHint是一个在JavaScript编写的程序中标记可疑用法的程序。 核心项目包括一个库本身以及作为Node模块分发的CLI程序。
JSHint是一个社区驱动的工具,用于检测JavaScript代码中的错误和潜在问题。由于JSHint非常灵活,您可以在期望执行代码的环境中轻松调整它。 JSHint是开源的,永远都是这样。
Name With Owner | jshint/jshint |
---|---|
Primary Language | JavaScript |
Program language | JavaScript (Language Count: 2) |
Platform | |
License: | MIT License |
Created At | 2011-01-19 22:28:53 |
---|---|
Pushed At | 2025-02-13 17:18:03 |
Last Commit At | |
Release Count | 85 |
Last Release Name | 2.13.6 (Posted on 2022-11-11 14:07:19) |
First Release Name | 2011-04-16 (Posted on 2011-04-16 10:05:33) |
Stargazers Count | 9k |
---|---|
Watchers Count | 289 |
Fork Count | 1.6k |
Commits Count | 2.3k |
Has Issues Enabled | |
Issues Count | 2423 |
Issue Open Count | 393 |
Pull Requests Count | 527 |
Pull Requests Open Count | 64 |
Pull Requests Close Count | 626 |
Has Wiki Enabled | |
---|---|
Is Archived | |
Is Fork | |
Is Locked | |
Is Mirror | |
Is Private |
[ 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 open source and
will always stay this way.
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.
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:
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.
Engineers from these companies and projects use JSHint:
And many more!
Most files are published using the standard MIT Expat
license. One file,
however, is provided under a slightly modified version of that license. The
so-called JSON license
is a non-free license, and unfortunately, we can't change it due to historical
reasons. This license is included as an in-line within the file it concerns.
JSHint is currently maintained by Rick Waldron,
Caitlin Potter, Mike
Pennisi, and Luke
Page. You can reach them via admin@jshint.org.
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 Sherov. We appreciate their long-term
commitment!
We really appreciate all kinds of feedback and contributions. Thanks for using and supporting JSHint!