ESLint vs Review Board vs SonarQube

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

ESLint

30.2K
13.8K
+ 1
28
Review Board

20
52
+ 1
6
SonarQube

1.7K
2K
+ 1
53

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

Advice on ESLint, Review Board, and SonarQube
Needs advice
on
ESLintESLintSass Lint Sass Lint
and
StylelintStylelint

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.

See more
Replies (3)
Amaro Mariño
Senior Frontend Developer at Landbot.io · | 6 upvotes · 165.2K views
Recommends
on
ESLintESLint

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.

See more
Alex Spieslechner

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 ;)

See more
Alexis Villegas Torres
Software Engineer at SpeedUrWeb · | 5 upvotes · 164.8K views
Recommends
on
StylelintStylelint

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!, :)

See more
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of ESLint
Pros of Review Board
Pros of SonarQube
  • 8
    Consistent javascript - opinions don't matter anymore
  • 6
    Free
  • 6
    IDE Integration
  • 4
    Customizable
  • 2
    Focuses code review on quality not style
  • 2
    Broad ecosystem of support & users
  • 3
    Simple to use. Great UI
  • 1
    Review Bots
  • 1
    Diff between review versions
  • 1
    Open Source
  • 26
    Tracks code complexity and smell trends
  • 16
    IDE Integration
  • 9
    Complete code Review
  • 2
    Difficult to deploy

Sign up to add or upvote prosMake informed product decisions

Cons of ESLint
Cons of Review Board
Cons of SonarQube
    Be the first to leave a con
      Be the first to leave a con
      • 7
        Sales process is long and unfriendly
      • 7
        Paid support is poor, techs arrogant and unhelpful
      • 1
        Does not integrate with Snyk

      Sign up to add or upvote consMake informed product decisions

      2.5K
      6.8K
      16
      174
      176
      91
      11.9K

      What is ESLint?

      A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.

      What is Review Board?

      Review Board is an open source, web-based code and document review tool built to help companies, open source projects, and other organizations keep their quality high and their bug count low.

      What is SonarQube?

      SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving.

      Need advice about which tool to choose?Ask the StackShare community!

      What companies use ESLint?
      What companies use Review Board?
      What companies use SonarQube?

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with ESLint?
      What tools integrate with Review Board?
      What tools integrate with SonarQube?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      Blog Posts

      What are some alternatives to ESLint, Review Board, and SonarQube?
      TSLint
      An extensible static analysis tool that checks TypeScript code for readability, maintainability, and functionality errors. It is widely supported across modern editors & build systems and can be customized with your own lint rules, configurations, and formatters.
      Prettier
      Prettier is an opinionated code formatter. It enforces a consistent style by parsing your code and re-printing it with its own rules that take the maximum line length into account, wrapping code when necessary.
      JSLint
      It is a static code analysis tool used in software development for checking if JavaScript source code complies with coding rules. It is provided primarily as a browser-based web application accessible through their domain, but there are also command-line adaptations.
      JSHint
      It is a community-driven tool to detect errors and potential problems in JavaScript code. It is open source and can easily adjust in the environment you expect your code to execute.
      Babel
      Babel will turn your ES6+ code into ES5 friendly code, so you can start using it right now without waiting for browser support.
      See all alternatives