ESLint vs TSLint

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


+ 1

+ 1
Add tool

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:

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

Advice on ESLint and TSLint
Needs advice
ESLintESLintSass Lint Sass Lint

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 · | 6 upvotes · 155.7K views

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:

And in order to avoid conflicts between Prettier and Eslint, you can use this config:

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 · 155.3K views

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,, 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 StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of ESLint
Pros of TSLint
  • 8
    Consistent javascript - opinions don't matter anymore
  • 6
  • 6
    IDE Integration
  • 4
  • 2
    Focuses code review on quality not style
  • 2
    Broad ecosystem of support & users
    Be the first to leave a pro

    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 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.

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

    What companies use ESLint?
    What companies use TSLint?
    See which teams inside your own company are using ESLint or TSLint.
    Sign up for StackShare EnterpriseLearn More

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

    What tools integrate with ESLint?
    What tools integrate with TSLint?

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

    Blog Posts

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