Need advice about which tool to choose?Ask the StackShare community!
ESLint vs JSHint: What are the differences?
Introduction ESLint and JSHint are both popular JavaScript linting tools that help developers identify and fix code errors, enforce coding conventions, and maintain code quality. While they have similar goals, there are key differences between the two.
Architecture: ESLint is built with a pluggable architecture, allowing developers to add or create custom rules. This flexibility enables ESLint to accommodate different coding styles and standards. On the other hand, JSHint has a more rigid architecture and does not have the same level of customizability.
Community support: ESLint has a larger and more active community compared to JSHint. This means that there are more resources, plugins, and rule sets available for ESLint, making it easier to find solutions to specific needs. JSHint, while still supported, has a smaller community and may have fewer resources and updates.
ES2015+ support: ESLint has better support for the latest ECMAScript standards, including ES2015 and beyond. It can handle syntax and rules specific to these newer versions of JavaScript. JSHint, on the other hand, has limited support for these modern language features.
Configurability: ESLint provides a highly configurable setup, allowing developers to specify and fine-tune their linting rules, environments, and plugins. This level of configurability makes ESLint suitable for large-scale projects with specific requirements. JSHint, while configurable to some extent, has fewer options for customization.
Error reporting: ESLint provides more granular and detailed error reporting. It can identify specific line numbers and code locations where issues occur, making it easier for developers to track down and fix problems. JSHint, while also capable of reporting errors, may provide less detailed information about the exact location of the issue.
Integration: ESLint integrates well with various development tools, build systems, and editors, making it easier to incorporate into different workflows. It has extensive support for popular frameworks such as React and Vue.js. JSHint, while it can be used alongside other tools, may have less seamless integration with modern development environments.
In summary, ESLint offers a more customizable and extensible linting solution with better community support and modern JavaScript language feature compatibility compared to JSHint.
Scenario: I want to integrate Prettier in our code base which is currently using ESLint (for .js and .scss both). The project is using gulp.
It doesn't feel quite right to me to use ESLint, I wonder if it would be better to use Stylelint or Sass Lint instead.
I completed integrating ESLint + Prettier, Planning to do the same with [ Stylelint || Sasslint || EsLint] + Prettier.
And have gulp 'fix' on file save (Watcher).
Any recommendation is appreciated.
In the case of .js files I would recommend using both Eslint and Prettier.
You can set up Prettier as an Eslint rule using the following plugin:
https://github.com/prettier/eslint-plugin-prettier
And in order to avoid conflicts between Prettier and Eslint, you can use this config:
https://github.com/prettier/eslint-config-prettier
Which turns off all Eslint rules that are unnecessary or might conflict with Prettier.
Pura vida! Well, I had a similar issue and at the end I decided to use Stylelint + Prettier for that job, in our case, we wanted that our linting process includes the SCSS files and not only the JS file, base on that we concluded that using only ESLint to do both things wasn't the best option, so, we integrated prettier with Stylelint, and for that we used a neat plugin that allowed us to use Prettier inside Stylelint here is the link, https://github.com/prettier/stylelint-prettier#recommended-configuration, I hope that this can help you, hasta pronto!, :)
you don't actually have to choose between these tools as they have vastly different purposes. i think its more a matter of understanding how to use them.
while eslint and stylelint are used to notify you about code quality issues, to guide you to write better code, prettier automatically handles code formatting (without notifying me). nothing else.
prettier and eslint both officially discourage using the eslint-plugin-prettier way, as these tools actually do very different things. autofixing with linters on watch isnt a great idea either. auto-fixing should only be done intentionally. you're not alone though, as a lot of devs set this up wrong.
i encourage you to think about what problem you're trying to solve and configure accordingly.
for my teams i set it up like this: - eslint, stylelint, prettier locally installed for cli use and ide support - eslint config prettier (code formatting rules are not eslints business, so dont warn me about it) - vscode workspace config: format on save - separate npm scripts for linting, and formatting - precommit hooks (husky)
so you can easily integrate with gulp. its just js after all ;)
Pros of ESLint
- Consistent javascript - opinions don't matter anymore8
- Free6
- IDE Integration6
- Customizable4
- Focuses code review on quality not style2
- Broad ecosystem of support & users2
Pros of JSHint
Sign up to add or upvote prosMake informed product decisions
Cons of ESLint
Cons of JSHint
- Non-intuitive configuration1
Sign up to add or upvote consMake informed product decisions
What is ESLint?
What is JSHint?
Need advice about which tool to choose?Ask the StackShare community!
What companies use JSHint?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with JSHint?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+43