Need advice about which tool to choose?Ask the StackShare community!
ESLint vs Review Board vs SonarQube: What are the differences?
Introduction
ESLint, Review Board, and SonarQube are tools used in the software development process to maintain code quality and identify issues.
Focus: ESLint mainly focuses on identifying and fixing problems in JavaScript code by enforcing coding styles and rules, whereas Review Board is primarily used for code review processes, collaboration, and managing project changes. SonarQube, on the other hand, provides a comprehensive code quality analysis covering multiple languages such as Java, C#, JavaScript, and more.
Integration: ESLint is integrated into the development workflow through plugins in popular IDEs like Visual Studio Code, while Review Board integrates with version control systems like Git, providing a platform for peer code review. SonarQube can be integrated into continuous integration pipelines to automatically analyze code quality and identify issues before deployment.
Automation: ESLint is more suitable for developers seeking real-time feedback as it lints code during development, whereas Review Board requires manual intervention for code review initiation. SonarQube offers automated code analysis and can generate reports on code smells, security vulnerabilities, and bugs without manual intervention.
Scope: ESLint mainly focuses on the syntax and structure of JavaScript code, helping developers write cleaner and error-free code, while Review Board is tailored for managing code review processes within teams to ensure code quality and knowledge sharing. SonarQube provides a broader spectrum of code quality analysis, covering various aspects such as security, reliability, and maintainability across multiple programming languages.
Reporting: ESLint generates reports highlighting errors, warnings, and suggestions for improving code quality within JavaScript projects. Review Board tracks code changes, discussions, and approvals in a collaborative environment. SonarQube generates detailed reports with metrics, trends, and actionable insights to help developers and teams make informed decisions on code improvements and maintenance.
Community Support: ESLint has a strong community focus with active maintenance and frequent updates to address the evolving JavaScript ecosystem. Review Board and SonarQube also have active communities, but their primary focus is on providing code review and code quality analysis tools with continuous improvements based on user feedback.
In Summary, ESLint, Review Board, and SonarQube serve distinct purposes in the software development lifecycle, focusing on code quality improvement through linting, code review, and comprehensive analysis across various programming languages.
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.
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 ;)
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!, :)
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 Review Board
- Simple to use. Great UI3
- Review Bots1
- Diff between review versions1
- Open Source1
Pros of SonarQube
- Tracks code complexity and smell trends26
- IDE Integration16
- Complete code Review9
- Difficult to deploy2
Sign up to add or upvote prosMake informed product decisions
Cons of ESLint
Cons of Review Board
Cons of SonarQube
- Sales process is long and unfriendly7
- Paid support is poor, techs arrogant and unhelpful7
- Does not integrate with Snyk1