JSHint Reviews & Product Details

JSHint allows you to enforce coding styles in your project that all team members are supposed to abide by. It helps to show error messages that might not be caught until the your code is compiled. Generally JSLint improve overall productivity with a project team Review collected by and hosted on G2.com.

It will show some error messages or warning that are unnecessary because they don't make your code fail. So you either have to ignore them of turn the offline which might require you to look at a documentation for turning off a specific error warning in JSHint Review collected by and hosted on G2.com.

JsHint can be used to enforce coding styles, to avoid unintended errors such as white listing global variables, flagging used variables, enforcing curly braces on loops and if statement blocks. Review collected by and hosted on G2.com.

Turning rules on and off for specific lines of code or a given block is a pain because you have to search for the name of the rule. Review collected by and hosted on G2.com.

JSHint helps me to code faster in my IDEs. It helps to ensure quality code and code that is lacking silly errors that otherwise is only found through testing. Review collected by and hosted on G2.com.

It lacks some of the edge-case configuration that I wanted and could potentially use a bit easier path to configure, for other users less used to manual config files, as well as I've found getting my fellow developers to adopt JSHint takes some work for those with less command-line experience. Additionally, it is a bit slow when dealing with large code-bases. Review collected by and hosted on G2.com.

I like that plugins for the software are available for the current editor I use, Vim. Not only that, it also supports other editors too. It could also function without one and go directly to the terminal. Review collected by and hosted on G2.com.

What I dislike about JSHint is it's speed and configurability. I've used other linters to especially ESLint and I could really see the difference in the speed the two has. With our hude codebase comprising of mostly javascript stuff, I found eslint better when it comes to customisability and speed. Review collected by and hosted on G2.com.

This tool fulfills an actual problem, debugging javascript. Many IDEs don't have an easy to use javascript debugger. JSHint not only provides errors in code but shares how many variables are unused. Review collected by and hosted on G2.com.

While the errors and warnings are easy to read and decipher, it might be nice to have them more color coded than all in grey. Review collected by and hosted on G2.com.

I like how JSHint can be used to quickly perform linting on some scratch code I quickly threw together. Moreover, I like how it’s not as extreme about it’s rules as JSLint. Review collected by and hosted on G2.com.

I don’t like that it doesn’t have the customization features that ESLint offers. Review collected by and hosted on G2.com.

The best in JSHint - it complies your javascript code and analyze with the defined coding rules.

It is greatly being distribute to the node.js community, so it will become an ease for any developer to just called it from the node.js.

The linting Process is quite amazing and easily being integrated to the website or webapp development flow.

It become a necessity to write the 'use strict' so that the strict context prevents certain actions from being taken and throws more exceptions.

It shows the error trace and exceptions trace which make it easy for the developer to find the where the actual error is occurring.

We have also ES6 support in this. Review collected by and hosted on G2.com.

Nothing to dislike in JSHint but some few things are there to get it disliking to raise a bit.

1. We can't determine which rule is causing an error if your configuration is too large.

2.Configuration is slightly confusing for new beginners.

3.Nothing to do with custom rules as such there is no support for the custom rules in the JsHint,

Review collected by and hosted on G2.com.

Simple to use and manipulate, it offers its functionality in a web application, discovers and alerts the most common errors, you can configure it by default in your projects and to ensure code quality among developers in a team, it ensures best practices and better maintainable code. Review collected by and hosted on G2.com.

It has little support for ES6, sometimes it can take time in code analysis in large projects, few options. Review collected by and hosted on G2.com.

Makes writing javascript a lot easier and also helps ensure best practices. Not only is syntax checked for but also if there is some code smell it will alert you. The configuration options are awesome to adjust settings per project and ensure standards on whatever project you are working on. Review collected by and hosted on G2.com.

Sometimes the rules it adheres to are debatable and could be argued for a different implementation or standard. It's a bit opinionated in how it thinks you should write javascript and that can be a bit constricting sometimes. Review collected by and hosted on G2.com.

It's easy to use, it detects common JS errors, you can configure it to ignore some errors, it runs fast and has descriptive errors messages, you can use it to enforce code quality among multiple team members. Review collected by and hosted on G2.com.

Nothing so far, maybe the fact that it doens't support ES6 well. Review collected by and hosted on G2.com.