Need advice about which tool to choose?Ask the StackShare community!
ESLint vs TSLint: What are the differences?
ESLint and TSLint are both static code analysis tools that help developers identify and fix issues in their code. However, there are several key differences between the two:
JavaScript vs TypeScript: The most significant difference between ESLint and TSLint is the language they support. ESLint is designed for JavaScript, while TSLint is specifically tailored for TypeScript. Although ESLint can analyze TypeScript code to some extent, TSLint provides more comprehensive analysis and enforcement for TypeScript-specific features.
Extensibility: ESLint has a more mature and extensive ecosystem of plugins and rules, making it highly customizable and adaptable to different project requirements. On the other hand, TSLint has a more limited range of available rules and plugins, as it is primarily focused on TypeScript-specific checks.
Maintenance and Future: ESLint has a larger and more active community compared to TSLint, which means it receives more frequent updates, bug fixes, and new features. On the other hand, TSLint is considered a legacy tool by its maintainers, and its future development is being phased out in favor of ESLint, which is officially recommended by the TypeScript team.
Integration: ESLint has better integration with popular code editors and build tools, making it easier to incorporate into different development workflows. TSLint, on the other hand, may require additional configuration and setup to work seamlessly with certain tools and editors.
Rules and checks: While both ESLint and TSLint provide a wide range of default rules and checks, their specific implementations and configurations differ. ESLint focuses on enforcing best practices, code style guidelines, and possible errors, while TSLint offers additional checks specific to TypeScript language features and design patterns.
Migration to ESLint: The TypeScript team officially recommends migrating from TSLint to ESLint for TypeScript projects. This migration involves configuring ESLint with TypeScript-specific plugins and rules to replicate the checks performed by TSLint. The migration process ensures a smoother transition for projects and ensures compatibility with future TypeScript language updates.
In summary, ESLint is designed for JavaScript and boasts a larger community and broader range of plugins compared to TSLint, which is specifically tailored for TypeScript. While both offer various rules and checks, ESLint focuses on general best practices, while TSLint emphasizes TypeScript specifics.
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 TSLint
Sign up to add or upvote prosMake informed product decisions
What is ESLint?
What is TSLint?
Need advice about which tool to choose?Ask the StackShare community!
What companies use TSLint?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with TSLint?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+43