Popularity

7.9

Declining

Activity

0.0

Stars 8,913

Watchers 296

Forks 1,757

Last Commit about 1 month ago

Description

[ Use it online • Docs • FAQ • Install • Contribute • Blog • Twitter ]

JSHint is a community-driven tool to detect errors and potential problems in JavaScript code and to enforce your team's coding conventions. It is very flexible so you can easily adjust it to your particular coding guidelines and the environment you expect your code to execute in. JSHint is open source and will always stay this way.

Code Quality Rank: L1

Monthly Downloads: 0

Programming language: JavaScript

License: MIT License

Tags: QA Tools

Latest version: v2.13.5

JSHint alternatives and similar libraries

Based on the "QA Tools" category.
Alternatively, view JSHint alternatives based on common mentions on social networks and blogs.

prettier

9.7 9.8 JSHint VS prettier

Prettier is an opinionated code formatter.
ESLint

9.4 9.5 L1 JSHint VS ESLint

Find and fix problems in your JavaScript code.

Appwrite - The open-source backend cloud platform

The open-source backend cloud platform for developing Web, Mobile, and Flutter applications. You can set up your backend faster with real-time APIs for authentication, databases, file storage, cloud functions, and much more!

Promo appwrite.io

husky

9.4 7.8 JSHint VS husky

Git hooks made easy 🐶 woof!
JS-Beautifier

7.7 5.6 JSHint VS JS-Beautifier

Beautifier for javascript
jscs

6.4 0.0 L4 JSHint VS jscs

JavaScript Code Style checker.
JSLint

5.8 6.1 L1 JSHint VS JSLint

JSLint, The JavaScript Code Quality and Coverage Tool
jsinspect

5.3 0.0 L5 JSHint VS jsinspect

Detect copy-pasted and structurally similar code
jsfmt

4.0 0.0 L5 JSHint VS jsfmt

For formatting, searching, and rewriting JavaScript.
dotenv-linter

4.0 0.0 JSHint VS dotenv-linter

⚡️Lightning-fast linter for .env files. Written in Rust 🦀
Typefont

3.8 0.0 JSHint VS Typefont

The first open-source library that detects the font of a text in a image.
buddy.js

3.0 0.0 L5 JSHint VS buddy.js

Magic number detection for JavaScript
Pre-evaluate code at buildtime

1.3 0.0 JSHint VS Pre-evaluate code at buildtime

Pre-evaluate code at build-time with babel-macros
JavaScript Standard Style

- JSHint VS JavaScript Standard Style

Opinionated, no-configuration style guide, style checker, and formatter

* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.

Do you think we are missing an alternative of JSHint or a related project?

Add another 'QA Tools' Library

Popular Comparisons

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:

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 Sherov. We appreciate their long-term commitment!