ESLint vs Infer vs SonarQube

Get Advice Icon

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

ESLint

30.2K
13.8K
+ 1
28
Infer

18
69
+ 1
0
SonarQube

1.7K
2K
+ 1
53

ESLint vs Infer vs SonarQube: What are the differences?

# Introduction

## Key Differences between ESLint, Infer, and SonarQube

1. **Analysis Focus**: ESLint is focused on analyzing JavaScript code for potential errors and maintaining code consistency through coding rules. Infer, on the other hand, is designed for static analysis of C, C++, and Objective-C code to identify bugs and performance issues. SonarQube offers a more diverse range of functionalities, including code quality analysis, security vulnerability detection, and continuous inspection of various programming languages.

2. **Integration with CI/CD**: ESLint can be easily integrated into Continuous Integration/Continuous Deployment (CI/CD) pipelines to enforce code quality standards. Infer also provides integration options with various build systems and CI tools for automated code analysis. SonarQube excels in its integration capabilities with popular CI platforms like Jenkins, Azure DevOps, and GitHub Actions for seamless code analysis and quality management within the development workflow.

3. **Supported Languages**: ESLint is specifically tailored for analyzing JavaScript codebases. In contrast, Infer is primarily focused on supporting C, C++, and Objective-C languages. SonarQube, being a comprehensive code analysis tool, supports a wide range of programming languages, including Java, C#, Python, PHP, and more.

4. **Code Coverage Analysis**: While ESLint and Infer primarily focus on static code analysis, SonarQube offers a holistic approach by including code coverage analysis to track the proportion of code exercised by automated tests. This feature helps in identifying untested code segments and improving overall code quality through effective test coverage.

5. **Community Support and Extensibility**: ESLint has a robust community backing, which continually contributes to the development of new rules and plugins to enhance code analysis capabilities. Infer also benefits from an active community that supports the tool's evolution and extension possibilities. Similarly, SonarQube provides a vibrant ecosystem of plugins and extensions to customize code analysis based on specific project requirements.

6. **Scalability and Enterprise Usage**: SonarQube stands out in terms of scalability and enterprise-grade usage with features like project portfolio management, centralized administration, and role-based access controls. ESLint and Infer are more suitable for smaller to mid-sized projects, whereas SonarQube caters to the needs of large organizations and complex codebases.

In Summary, the key differences between ESLint, Infer, and SonarQube lie in their analysis focus, integration capabilities, supported languages, code coverage analysis, community support, and scalability for enterprise usage.

Advice on ESLint, Infer, 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 · 166.1K 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 · 165.6K 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 Infer
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
    Be the first to leave a pro
    • 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 Infer
    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
        11
        51
        2
        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 Infer?

        Facebook Infer is a static analysis tool - if you give Infer some Objective-C, Java, or C code, it produces a list of potential bugs. Anyone can use Infer to intercept critical bugs before they have shipped to people's phones, and help prevent crashes or poor performance.

        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 Infer?
        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 Infer?
        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, Infer, 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