ESLint vs Standard JS

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

ESLint

15.5K
8.6K
+ 1
23
Standard JS

58
72
+ 1
1
Add tool

ESLint vs Standard JS: What are the differences?

What is ESLint? The fully pluggable JavaScript code quality tool. A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.

What is Standard JS? A JavaScript Standard Style. It is a Style guide, with linter & automatic code fixer. It is a way to enforce consistent style in your project. It automatically formats code.

ESLint and Standard JS belong to "Code Review" category of the tech stack.

ESLint is an open source tool with 14.4K GitHub stars and 2.47K GitHub forks. Here's a link to ESLint's open source repository on GitHub.

Asana, Rainist, and Intuit are some of the popular companies that use ESLint, whereas Standard JS is used by NodeSource, commonality, and Stickermule. ESLint has a broader approval, being mentioned in 544 company stacks & 594 developers stacks; compared to Standard JS, which is listed in 6 company stacks and 3 developer stacks.

Advice on ESLint and Standard JS
Needs advice
on
StylelintStylelintSass Lint Sass Lint
and
ESLintESLint

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 · 62.2K views
Recommends
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
Alexis Villegas Torres
Software Engineer at SpeedUrWeb · | 5 upvotes · 62.1K views
Recommends
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
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
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of ESLint
Pros of Standard JS
  • 7
    Consistent javascript - opinions don't matter anymore
  • 5
    IDE Integration
  • 4
    Free
  • 3
    Customizable
  • 2
    Focuses code review on quality not style
  • 2
    Broad ecosystem of support & users
  • 1
    Free
  • 0
    Customizable

Sign up to add or upvote prosMake 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 Standard JS?

It is a Style guide, with linter & automatic code fixer. It is a way to enforce consistent style in your project. It automatically formats code.

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

What companies use ESLint?
What companies use Standard JS?
See which teams inside your own company are using ESLint or Standard JS.
Sign up for Private StackShareLearn More

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

What tools integrate with ESLint?
What tools integrate with Standard JS?
    No integrations found

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

    Blog Posts

    What are some alternatives to ESLint and Standard JS?
    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