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

ESLint

30K
13.7K
+ 1
28
SonarLint

173
350
+ 1
16
Add tool

ESLint vs SonarLint: What are the differences?

ESLint and SonarLint are two popular static code analysis tools to identify and fix code quality issues. Let's explore the key differences between the two:

  1. Integration: ESLint is a flexible JavaScript linter that seamlessly integrates with popular editors, IDEs, and build tools. It offers extensive customization options, allowing developers to configure linting rules based on their project requirements. On the other hand, SonarLint is deeply integrated with the SonarQube platform, providing centralized code analysis and reporting within the SonarQube ecosystem.

  2. Code Analysis Capabilities: ESLint focuses on JavaScript code analysis, enforcing coding standards, and identifying potential issues. SonarLint offers comprehensive code analysis across multiple languages, including security vulnerabilities, code duplications, and architectural concerns. It provides a broader range of rules and metrics to assess code quality.

  3. Integration with Code Quality Platform: ESLint can be used in conjunction with other tools or integrated into CI/CD pipelines for continuous analysis. SonarLint tightly integrates with the SonarQube platform, offering a centralized dashboard to manage code quality, track issues, and generate reports. It ensures consistent coding standards and allows monitoring of code quality metrics organization-wide.

  4. Rule Sets and Customization: ESLint provides predefined and customizable rules, allowing developers to enforce preferred coding standards. It supports plugins and sharable configurations. SonarLint utilizes rule sets from SonarQube with limited customization options for rule sets and quality profiles.

In summary, ESLint and SonarLint are static code analysis tools that help developers improve code quality. ESLint is a highly configurable JavaScript linter that can be integrated into various development environments, while SonarLint is tightly integrated with the SonarQube platform and provides more comprehensive code analysis capabilities for multiple programming languages.

Advice on ESLint and SonarLint
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 · 163.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 · 162.7K 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 SonarLint
  • 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
  • 13
    IDE Integration
  • 3
    Free

Sign up to add or upvote prosMake informed product decisions

Cons of ESLint
Cons of SonarLint
    Be the first to leave a con
    • 3
      Non contextual warnings
    • 3
      Not Very User Friendly

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    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 SonarLint?

    It is an IDE extension that helps you detect and fix quality issues as you write code. Like a spell checker, it squiggles flaws so that they can be fixed before committing code.

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

    What companies use ESLint?
    What companies use SonarLint?
    Manage your open source components, licenses, and vulnerabilities
    Learn More

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

    What tools integrate with ESLint?
    What tools integrate with SonarLint?

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

    Blog Posts

    What are some alternatives to ESLint and SonarLint?
    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.
    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.
    See all alternatives