Need advice about which tool to choose?Ask the StackShare community!
ESLint vs Reek: What are the differences?
1. Configuration: ESLint allows for extensive customization through its configuration options, including specifying coding styles, enforcing certain rules, and enabling plugins. On the other hand, Reek has a simpler configuration setup that focuses mainly on detecting code smells and anti-patterns in Ruby code. 2. Language Support: ESLint is primarily used for JavaScript, but it also supports JSX, TypeScript, and other languages. Reek, on the other hand, is specifically designed for Ruby and does not support other languages. 3. Rule Coverage: ESLint has a vast library of rules that cover a wide range of coding practices and patterns, providing a comprehensive tool for static code analysis. In contrast, Reek focuses more on specific code smells and common anti-patterns, offering a more specialized approach to code quality analysis. 4. Community and Support: ESLint has a large community of users and contributors, with extensive documentation, plugins, and integrations available. Reek, while actively maintained, has a smaller user base and may have limited third-party support compared to ESLint. 5. Integration: ESLint integrates seamlessly with most modern IDEs, text editors, and build tools, making it easier to incorporate into existing development workflows. Reek, on the other hand, may require additional setup or customization to integrate effectively with other tools and environments. 6. Performance: ESLint is known for its speed and efficiency in analyzing codebases of varying sizes, making it suitable for large-scale projects. Reek, being more focused on specific code smells, may have different performance characteristics and may be better suited for smaller codebases or specific Ruby applications.
In Summary, ESLint and Reek differ in configuration options, language support, rule coverage, community size, integration capabilities, and performance characteristics.
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 Reek
Sign up to add or upvote prosMake informed product decisions
What is ESLint?
What is Reek?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Reek?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Reek?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+43