eslint vs @typescript-eslint/eslint-plugin vs tslint vs jshint vs jslint
JavaScript and TypeScript Linting Tools Comparison
1 Year
eslint@typescript-eslint/eslint-plugintslintjshintjslintSimilar Packages:
What's JavaScript and TypeScript Linting Tools?

Linting tools are essential in web development to analyze code for potential errors, enforce coding standards, and improve overall code quality. They help identify issues such as syntax errors, stylistic inconsistencies, and potential bugs before the code is executed. This proactive approach to code quality can lead to more maintainable, readable, and error-free codebases. Linting tools can be integrated into development workflows, IDEs, and CI/CD pipelines, providing real-time feedback to developers and promoting best practices across teams. Popular linting tools include ESLint, JSHint, JSLint, TSLint, and @typescript-eslint/eslint-plugin, each with its own features and focus areas.

Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
eslint46,671,93625,6083.47 MB91a month agoMIT
@typescript-eslint/eslint-plugin36,797,09615,5342.34 MB357a month agoMIT
tslint1,905,6065,901-15 years agoApache-2.0
jshint599,2039,0063.31 MB456-MIT
jslint72,918491-196 years agoBSD-3-Clause
Feature Comparison: eslint vs @typescript-eslint/eslint-plugin vs tslint vs jshint vs jslint

Language Support

  • eslint:

    ESLint is primarily focused on JavaScript linting but also supports TypeScript through additional plugins. It is highly versatile and can be configured to lint various JavaScript dialects, including ES6, JSX, and more. ESLint's extensibility allows it to adapt to different languages and frameworks.

  • @typescript-eslint/eslint-plugin:

    @typescript-eslint/eslint-plugin provides linting support for TypeScript code, allowing you to enforce TypeScript-specific rules and best practices alongside general JavaScript linting. It is designed to work seamlessly with ESLint and enhances its capabilities for TypeScript projects.

  • tslint:

    TSLint was a linting tool specifically designed for TypeScript code. It provided rules and checks tailored for TypeScript, but it has been deprecated in favor of @typescript-eslint, which integrates TypeScript linting into the ESLint ecosystem.

  • jshint:

    JSHint is a linting tool for JavaScript that focuses on identifying potential issues in code. It does not support TypeScript or other languages. JSHint is best suited for traditional JavaScript projects and provides configurable rules to catch common coding mistakes.

  • jslint:

    JSLint is a JavaScript-only linting tool that enforces a strict set of coding standards. It does not support TypeScript or other languages. JSLint is known for its opinionated approach and is best used in projects where adherence to specific coding conventions is required.

Configurability

  • eslint:

    ESLint is highly configurable, allowing developers to define their own rules, set severity levels, and create custom configurations. It supports configuration files in various formats (JSON, YAML, JavaScript) and allows for per-directory or per-file rule overrides, making it one of the most flexible linting tools available.

  • @typescript-eslint/eslint-plugin:

    @typescript-eslint/eslint-plugin allows for extensive configurability of TypeScript linting rules within the ESLint framework. You can customize rules, set severity levels, and create configuration files to suit your project's needs. It also supports combining TypeScript rules with existing ESLint rules for a more comprehensive linting setup.

  • tslint:

    TSLint was configurable, allowing users to enable or disable specific rules and set up configuration files. However, it lacked the flexibility and extensibility of ESLint, which is why it has been deprecated in favor of the @typescript-eslint project, which offers better configurability within the ESLint framework.

  • jshint:

    JSHint offers a moderate level of configurability, allowing users to enable or disable specific rules and set configuration options through a single file. However, it is less flexible than ESLint in terms of creating custom rules or plugins. JSHint's simplicity makes it easy to configure, but it lacks the depth of customization found in more modern linting tools.

  • jslint:

    JSLint is not configurable; it enforces a strict set of rules defined by its creator, Douglas Crockford. Users cannot change the rules or customize the linting process, which makes JSLint more of a tool for enforcing a specific coding style rather than a flexible linting solution. Its rigidity can be a drawback for teams that want to adapt the tool to their coding standards.

Integration with Build Tools

  • eslint:

    ESLint integrates well with various build tools, task runners, and CI/CD pipelines. It can be easily incorporated into workflows using tools like Webpack, Gulp, Grunt, and npm scripts. ESLint also has plugins for popular IDEs and text editors, providing real-time linting feedback during development.

  • @typescript-eslint/eslint-plugin:

    @typescript-eslint/eslint-plugin integrates seamlessly with ESLint, allowing it to be used alongside other ESLint plugins and tools. It can be easily integrated into build processes, CI/CD pipelines, and code editors to enforce TypeScript linting rules automatically.

  • tslint:

    TSLint integrated well with build tools and CI/CD pipelines, allowing for automated linting of TypeScript code as part of the build process. However, since TSLint has been deprecated, it is recommended to use @typescript-eslint for TypeScript linting in modern workflows.

  • jshint:

    JSHint can be integrated into build processes and CI/CD pipelines, but it is less commonly used in modern workflows compared to ESLint. JSHint can be run as part of automated testing scripts to ensure code quality before deployment.

  • jslint:

    JSLint can be integrated into build processes and CI/CD pipelines, but it is typically used as a standalone tool. Its strict nature makes it suitable for pre-commit hooks or automated checks to ensure code quality before merging changes.

Community and Ecosystem

  • eslint:

    ESLint has a large and active community, making it one of the most popular linting tools for JavaScript and TypeScript. It has a rich ecosystem of plugins, rules, and integrations, which are continuously maintained and updated by the community. ESLint's popularity ensures a wealth of resources, documentation, and support for developers.

  • @typescript-eslint/eslint-plugin:

    @typescript-eslint/eslint-plugin is part of the larger ESLint ecosystem and has a growing community of contributors. It is actively maintained and regularly updated to support the latest TypeScript features and best practices. The plugin benefits from the extensive ecosystem of ESLint, including third-party plugins and integrations.

  • tslint:

    TSLint had a strong community during its active development, but it has been deprecated in favor of @typescript-eslint. The community has largely migrated to the new project, which offers better support for TypeScript linting within the ESLint ecosystem.

  • jshint:

    JSHint has a smaller but dedicated community. It is actively maintained, but its popularity has declined in favor of more modern tools like ESLint. JSHint still has a loyal user base and provides good documentation and support for those who prefer its simplicity.

  • jslint:

    JSLint has a niche community, primarily around its creator, Douglas Crockford. It is not actively developed, and its usage has declined with the rise of more flexible and configurable linting tools. JSLint is still respected for its simplicity and effectiveness in enforcing coding standards, but it lacks the community-driven development of more modern tools.

Ease of Use: Code Examples

  • eslint:

    JavaScript linting with ESLint

    npm install --save-dev eslint
    
    // .eslintrc.json
    {
      "extends": "eslint:recommended",
      "rules": {
        "no-console": "warn"
      }
    }
    
    // example.js
    console.log("Hello, world!");
    
    npx eslint example.js
    
  • @typescript-eslint/eslint-plugin:

    TypeScript linting with @typescript-eslint/eslint-plugin

    npm install --save-dev eslint @typescript-eslint/parser @typescript-eslint/eslint-plugin
    
    // .eslintrc.json
    {
      "parser": "@typescript-eslint/parser",
      "extends": ["eslint:recommended", "plugin:@typescript-eslint/recommended"],
      "rules": {
        "@typescript-eslint/no-explicit-any": "warn"
      }
    }
    
    // example.ts
    const example: any = "Hello, world!";
    console.log(example);
    
    npx eslint example.ts
    
  • tslint:

    TypeScript linting with TSLint

    npm install --save-dev tslint
    
    // tslint.json
    {
      "extends": "tslint:recommended",
      "rules": {
        "no-console": true
      }
    }
    
    // example.ts
    const x: number = 10;
    console.log(x);
    
    npx tslint example.ts
    
  • jshint:

    JavaScript linting with JSHint

    npm install --save-dev jshint
    
    // .jshintrc
    {
      "esversion": 6,
      "node": true,
      "browser": true
    }
    
    // example.js
    var x = 10;
    console.log(x);
    
    npx jshint example.js
    
  • jslint:

    JavaScript linting with JSLint

    npm install --save-dev jslint
    
    // example.js
    "use strict";
    
    var x = 10;
    console.log(x);
    
    npx jslint example.js
    
How to Choose: eslint vs @typescript-eslint/eslint-plugin vs tslint vs jshint vs jslint
  • eslint:

    Select ESLint for a highly customizable and widely adopted linting solution for JavaScript (and TypeScript) projects. It offers a rich ecosystem of plugins and rules, making it suitable for both small and large codebases. ESLint is the go-to choice for modern JavaScript development, especially when working with frameworks like React, Vue, or Angular.

  • @typescript-eslint/eslint-plugin:

    Choose @typescript-eslint/eslint-plugin if you are working on a TypeScript project and want to enforce TypeScript-specific linting rules alongside general JavaScript rules. It is ideal for teams that want to maintain a consistent code style and catch TypeScript-related issues during development.

  • tslint:

    Select TSLint if you are working on a TypeScript project and need a dedicated linting tool for TypeScript code. However, note that TSLint has been deprecated in favor of @typescript-eslint, so it is recommended to use @typescript-eslint/eslint-plugin for TypeScript linting going forward.

  • jshint:

    Use JSHint if you need a simple and easy-to-configure linting tool for JavaScript. It is particularly useful for legacy projects or teams that want a straightforward solution without the complexity of extensive configuration. JSHint is less flexible than ESLint but provides quick feedback on common JavaScript issues.

  • jslint:

    Choose JSLint if you prefer a opinionated linting tool that enforces a strict set of coding standards. It is best suited for teams that want to adhere to a specific coding style and are willing to accept JSLint's limitations in terms of configurability. JSLint is known for its simplicity and effectiveness in catching common JavaScript errors.

README for eslint

npm version Downloads Build Status
Open Collective Backers Open Collective Sponsors

ESLint

Website | Configure ESLint | Rules | Contribute to ESLint | Report Bugs | Code of Conduct | Twitter | Discord | Mastodon | Bluesky

ESLint is a tool for identifying and reporting on patterns found in ECMAScript/JavaScript code. In many ways, it is similar to JSLint and JSHint with a few exceptions:

  • ESLint uses Espree for JavaScript parsing.
  • ESLint uses an AST to evaluate patterns in code.
  • ESLint is completely pluggable, every single rule is a plugin and you can add more at runtime.

Table of Contents

  1. Installation and Usage
  2. Configuration
  3. Version Support
  4. Code of Conduct
  5. Filing Issues
  6. Frequently Asked Questions
  7. Releases
  8. Security Policy
  9. Semantic Versioning Policy
  10. License
  11. Team
  12. Sponsors
  13. Technology Sponsors

Installation and Usage

Prerequisites: Node.js (^18.18.0, ^20.9.0, or >=21.1.0) built with SSL support. (If you are using an official Node.js distribution, SSL is always built in.)

You can install and configure ESLint using this command:

npm init @eslint/config@latest

After that, you can run ESLint on any file or directory like this:

npx eslint yourfile.js

pnpm Installation

To use ESLint with pnpm, we recommend setting up a .npmrc file with at least the following settings:

auto-install-peers=true
node-linker=hoisted

This ensures that pnpm installs dependencies in a way that is more compatible with npm and is less likely to produce errors.

Configuration

You can configure rules in your eslint.config.js files as in this example:

export default [
    {
        files: ["**/*.js", "**/*.cjs", "**/*.mjs"],
        rules: {
            "prefer-const": "warn",
            "no-constant-binary-expression": "error"
        }
    }
];

The names "prefer-const" and "no-constant-binary-expression" are the names of rules in ESLint. The first value is the error level of the rule and can be one of these values:

  • "off" or 0 - turn the rule off
  • "warn" or 1 - turn the rule on as a warning (doesn't affect exit code)
  • "error" or 2 - turn the rule on as an error (exit code will be 1)

The three error levels allow you fine-grained control over how ESLint applies rules (for more configuration options and details, see the configuration docs).

Version Support

The ESLint team provides ongoing support for the current version and six months of limited support for the previous version. Limited support includes critical bug fixes, security issues, and compatibility issues only.

ESLint offers commercial support for both current and previous versions through our partners, Tidelift and HeroDevs.

See Version Support for more details.

Code of Conduct

ESLint adheres to the OpenJS Foundation Code of Conduct.

Filing Issues

Before filing an issue, please be sure to read the guidelines for what you're reporting:

Frequently Asked Questions

Does ESLint support JSX?

Yes, ESLint natively supports parsing JSX syntax (this must be enabled in configuration). Please note that supporting JSX syntax is not the same as supporting React. React applies specific semantics to JSX syntax that ESLint doesn't recognize. We recommend using eslint-plugin-react if you are using React and want React semantics.

Does Prettier replace ESLint?

No, ESLint and Prettier have different jobs: ESLint is a linter (looking for problematic patterns) and Prettier is a code formatter. Using both tools is common, refer to Prettier's documentation to learn how to configure them to work well with each other.

What ECMAScript versions does ESLint support?

ESLint has full support for ECMAScript 3, 5, and every year from 2015 up until the most recent stage 4 specification (the default). You can set your desired ECMAScript syntax and other settings (like global variables) through configuration.

What about experimental features?

ESLint's parser only officially supports the latest final ECMAScript standard. We will make changes to core rules in order to avoid crashes on stage 3 ECMAScript syntax proposals (as long as they are implemented using the correct experimental ESTree syntax). We may make changes to core rules to better work with language extensions (such as JSX, Flow, and TypeScript) on a case-by-case basis.

In other cases (including if rules need to warn on more or fewer cases due to new syntax, rather than just not crashing), we recommend you use other parsers and/or rule plugins. If you are using Babel, you can use @babel/eslint-parser and @babel/eslint-plugin to use any option available in Babel.

Once a language feature has been adopted into the ECMAScript standard (stage 4 according to the TC39 process), we will accept issues and pull requests related to the new feature, subject to our contributing guidelines. Until then, please use the appropriate parser and plugin(s) for your experimental feature.

Which Node.js versions does ESLint support?

ESLint updates the supported Node.js versions with each major release of ESLint. At that time, ESLint's supported Node.js versions are updated to be:

  1. The most recent maintenance release of Node.js
  2. The lowest minor version of the Node.js LTS release that includes the features the ESLint team wants to use.
  3. The Node.js Current release

ESLint is also expected to work with Node.js versions released after the Node.js Current release.

Refer to the Quick Start Guide for the officially supported Node.js versions for a given ESLint release.

Where to ask for help?

Open a discussion or stop by our Discord server.

Why doesn't ESLint lock dependency versions?

Lock files like package-lock.json are helpful for deployed applications. They ensure that dependencies are consistent between environments and across deployments.

Packages like eslint that get published to the npm registry do not include lock files. npm install eslint as a user will respect version constraints in ESLint's package.json. ESLint and its dependencies will be included in the user's lock file if one exists, but ESLint's own lock file would not be used.

We intentionally don't lock dependency versions so that we have the latest compatible dependency versions in development and CI that our users get when installing ESLint in a project.

The Twilio blog has a deeper dive to learn more.

Releases

We have scheduled releases every two weeks on Friday or Saturday. You can follow a release issue for updates about the scheduling of any particular release.

Security Policy

ESLint takes security seriously. We work hard to ensure that ESLint is safe for everyone and that security issues are addressed quickly and responsibly. Read the full security policy.

Semantic Versioning Policy

ESLint follows semantic versioning. However, due to the nature of ESLint as a code quality tool, it's not always clear when a minor or major version bump occurs. To help clarify this for everyone, we've defined the following semantic versioning policy for ESLint:

  • Patch release (intended to not break your lint build)
    • A bug fix in a rule that results in ESLint reporting fewer linting errors.
    • A bug fix to the CLI or core (including formatters).
    • Improvements to documentation.
    • Non-user-facing changes such as refactoring code, adding, deleting, or modifying tests, and increasing test coverage.
    • Re-releasing after a failed release (i.e., publishing a release that doesn't work for anyone).
  • Minor release (might break your lint build)
    • A bug fix in a rule that results in ESLint reporting more linting errors.
    • A new rule is created.
    • A new option to an existing rule that does not result in ESLint reporting more linting errors by default.
    • A new addition to an existing rule to support a newly-added language feature (within the last 12 months) that will result in ESLint reporting more linting errors by default.
    • An existing rule is deprecated.
    • A new CLI capability is created.
    • New capabilities to the public API are added (new classes, new methods, new arguments to existing methods, etc.).
    • A new formatter is created.
    • eslint:recommended is updated and will result in strictly fewer linting errors (e.g., rule removals).
  • Major release (likely to break your lint build)
    • eslint:recommended is updated and may result in new linting errors (e.g., rule additions, most rule option updates).
    • A new option to an existing rule that results in ESLint reporting more linting errors by default.
    • An existing formatter is removed.
    • Part of the public API is removed or changed in an incompatible way. The public API includes:
      • Rule schemas
      • Configuration schema
      • Command-line options
      • Node.js API
      • Rule, formatter, parser, plugin APIs

According to our policy, any minor update may report more linting errors than the previous release (ex: from a bug fix). As such, we recommend using the tilde (~) in package.json e.g. "eslint": "~3.1.0" to guarantee the results of your builds.

License

MIT License

Copyright OpenJS Foundation and other contributors, <www.openjsf.org>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Team

These folks keep the project moving and are resources for help.

Technical Steering Committee (TSC)

The people who manage releases, review feature requests, and meet regularly to ensure ESLint is properly maintained.

Nicholas C. Zakas's Avatar
Nicholas C. Zakas
Francesco Trotta's Avatar
Francesco Trotta
Milos Djermanovic's Avatar
Milos Djermanovic

Reviewers

The people who review and implement new features.

唯然's Avatar
唯然
Nitin Kumar's Avatar
Nitin Kumar

Committers

The people who review and fix bugs and help triage issues.

Josh Goldberg ✨'s Avatar
Josh Goldberg ✨
Tanuj Kanti's Avatar
Tanuj Kanti

Website Team

Team members who focus specifically on eslint.org

Amaresh  S M's Avatar
Amaresh S M
Strek's Avatar
Strek
Percy Ma's Avatar
Percy Ma

Sponsors

The following companies, organizations, and individuals support ESLint's ongoing maintenance and development. Become a Sponsor to get your logo on our READMEs and website.

Platinum Sponsors

Automattic Airbnb

Gold Sponsors

Qlty Software trunk.io

Silver Sponsors

Vite JetBrains Liftoff American Express StackBlitz

Bronze Sponsors

Cybozu Anagram Solver Icons8 Discord GitBook Neko Nx Mercedes-Benz Group HeroCoders LambdaTest

Technology Sponsors

Technology sponsors allow us to use their products and services for free as part of a contribution to the open source ecosystem and our work.

Netlify Algolia 1Password