eslint vs prettier vs stylelint vs tslint vs jshint vs oxlint
JavaScript Linting and Formatting Tools Comparison
Search packages..
1 Year
eslintprettierstylelinttslintjshintoxlintSimilar Packages:
What's JavaScript Linting and Formatting Tools?

Linting and formatting tools are essential in web development as they help maintain code quality and consistency across projects. These tools analyze code for potential errors, enforce coding standards, and can automatically format code to improve readability and maintainability. They play a crucial role in collaborative environments where multiple developers contribute to the same codebase, ensuring that the code adheres to defined style guidelines and best practices.

Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
eslint62,530,85725,9972.95 MB798 days agoMIT
prettier55,895,99150,5067.88 MB1,4443 months agoMIT
stylelint5,978,94811,2611.65 MB1699 days agoMIT
tslint2,400,1465,901-15 years agoApache-2.0
jshint710,2419,0273.31 MB457-MIT
oxlint219,55114,64529.9 kB166a day agoMIT
Feature Comparison: eslint vs prettier vs stylelint vs tslint vs jshint vs oxlint

Configurability

  • eslint:

    ESLint is highly configurable, allowing developers to define their own rules and settings. It supports custom plugins and configurations, making it suitable for a wide range of projects and coding styles.

  • prettier:

    Prettier is opinionated and has minimal configuration options, focusing on consistent formatting rather than linting. It enforces a single style, which can be beneficial for teams looking for uniformity without debate.

  • stylelint:

    Stylelint is configurable and allows for custom rules specific to CSS and its preprocessors. It supports a variety of plugins to extend its functionality, making it versatile for styling needs.

  • tslint:

    TSLint provides a set of TypeScript-specific rules but is less configurable than ESLint. It is tailored for TypeScript projects, focusing on TypeScript-related issues.

  • jshint:

    JSHint offers a simpler configuration model, which is less flexible than ESLint but sufficient for basic linting needs. It allows for some customization but lacks the extensive plugin ecosystem of ESLint.

  • oxlint:

    OXLint is specifically designed for the Ox programming language, providing limited configurability focused on Ox syntax. It is not intended for general-purpose JavaScript linting.

Integration

  • eslint:

    ESLint integrates well with various build tools and IDEs, providing real-time feedback as you code. It is widely supported in editors like Visual Studio Code, making it a popular choice among developers.

  • prettier:

    Prettier integrates easily with many IDEs and can be run as part of the build process. It can also be combined with ESLint to handle both linting and formatting, providing a comprehensive solution.

  • stylelint:

    Stylelint supports integration with various build tools and IDEs, allowing for real-time linting of CSS files. It can also be combined with Prettier for a complete styling solution.

  • tslint:

    TSLint integrates with TypeScript projects and can be used alongside other tools, but its deprecation means that developers are encouraged to transition to ESLint for better support.

  • jshint:

    JSHint can be integrated into various development environments, but it may not have as seamless an integration experience as ESLint. It is suitable for quick checks but lacks advanced features.

  • oxlint:

    OXLint is designed for use with the Ox programming language and may have limited integration options compared to more widely used tools. Its usage is niche and specific.

Community Support

  • eslint:

    ESLint has a large and active community, with extensive documentation and a wealth of plugins available. This makes it easy to find support and resources for various use cases.

  • prettier:

    Prettier has gained significant popularity and has a strong community backing. It is well-documented, and many developers share configurations and best practices.

  • stylelint:

    Stylelint has a growing community and is well-supported with documentation. It is increasingly adopted in projects that require CSS linting, making it a solid choice for styling needs.

  • tslint:

    TSLint had a dedicated community, but with its deprecation, support is dwindling as developers move to ESLint for TypeScript linting.

  • jshint:

    JSHint has a smaller community compared to ESLint, but it still has a dedicated user base. Documentation is available, but it may not be as comprehensive as that of ESLint.

  • oxlint:

    OXLint has a very niche community, primarily focused on Ox programming. Resources and support may be limited due to its specialized nature.

Performance

  • eslint:

    ESLint is optimized for performance and can handle large codebases efficiently. It provides options for incremental linting and can be configured to run only on changed files, improving speed during development.

  • prettier:

    Prettier is designed for speed and can format large files quickly. It is optimized to handle code formatting without significant performance overhead, making it suitable for large projects.

  • stylelint:

    Stylelint is generally performant, but its efficiency can vary based on the complexity of the CSS being linted. It is designed to handle large stylesheets effectively.

  • tslint:

    TSLint's performance is adequate for TypeScript projects, but as it is being deprecated, users are encouraged to transition to ESLint for better performance and support.

  • jshint:

    JSHint performs well for smaller projects but may struggle with larger codebases due to its less efficient parsing and analysis compared to ESLint.

  • oxlint:

    OXLint's performance is tailored for the Ox programming language, but its efficiency will depend on the complexity of the Ox code being analyzed.

Learning Curve

  • eslint:

    ESLint has a moderate learning curve due to its extensive configuration options. However, once set up, it provides valuable feedback that can enhance coding practices.

  • prettier:

    Prettier is easy to adopt, with minimal configuration required. Its opinionated nature means that developers can quickly start using it without extensive setup.

  • stylelint:

    Stylelint has a moderate learning curve, especially for those new to CSS linting. However, its documentation helps ease the learning process.

  • tslint:

    TSLint is straightforward for TypeScript developers, but with its deprecation, new users are encouraged to learn ESLint instead.

  • jshint:

    JSHint is relatively easy to learn and use, making it a good choice for beginners or those looking for a straightforward linting solution.

  • oxlint:

    OXLint may have a steep learning curve for those unfamiliar with the Ox programming language, as it is specialized and not widely used.

How to Choose: eslint vs prettier vs stylelint vs tslint vs jshint vs oxlint
  • eslint:

    Choose ESLint if you need a highly configurable linter that supports modern JavaScript features and frameworks. It has a vast ecosystem of plugins and is widely adopted in the JavaScript community, making it suitable for both frontend and backend projects.

  • prettier:

    Choose Prettier if your primary goal is to enforce consistent code formatting across your project. It automatically formats code according to predefined rules, which can help reduce debates about code style among team members and streamline the development process.

  • stylelint:

    Choose Stylelint if you are focused on linting CSS and related files. It provides a powerful tool for enforcing consistent styles in stylesheets and can be integrated with various preprocessors like Sass and Less.

  • tslint:

    Choose TSLint if you are working with TypeScript projects. It offers TypeScript-specific linting rules and is designed to help catch common issues in TypeScript codebases, although it is being deprecated in favor of ESLint with TypeScript support.

  • jshint:

    Choose JSHint if you are looking for a straightforward linter that is easy to set up and use. It is less configurable than ESLint but can be a good option for smaller projects or legacy codebases that require basic linting without extensive configuration.

  • oxlint:

    Choose OXLint if you are working with a project that requires a linter specifically designed for the Ox programming language. It is tailored for Ox syntax and semantics, making it ideal for developers in that niche.

Similar Npm Packages to eslint

eslint is a widely used linting utility for JavaScript and JSX code. It helps developers identify and fix problems in their code by enforcing a consistent coding style and catching potential errors before they become issues. ESLint is highly configurable, allowing developers to define their own rules or use predefined configurations to suit their project's needs. While ESLint is an excellent tool for maintaining code quality, there are other alternatives that serve similar purposes. Here are a few notable alternatives:

  • prettier is an opinionated code formatter that focuses on maintaining a consistent style across your codebase. Unlike ESLint, which primarily focuses on identifying and fixing code quality issues, Prettier automatically formats your code according to a set of rules. It can be used alongside ESLint to ensure both code quality and consistent formatting, making it a popular choice among developers who want to streamline their development workflow.
  • stylelint is a modern linter specifically designed for CSS and other style-related files. It helps developers maintain consistent styles and catch errors in their stylesheets. If your project involves a significant amount of CSS or preprocessors like SCSS or LESS, using Stylelint in conjunction with ESLint can help ensure that both your JavaScript and styles are well-structured and error-free.
  • tslint was a linter specifically designed for TypeScript code. However, it has been deprecated in favor of ESLint, which now supports TypeScript through the use of plugins. If you are working on a TypeScript project, you can leverage ESLint's capabilities to lint your TypeScript code effectively, making TSLint less relevant in modern development.

For a comprehensive comparison of these packages, visit: Comparing eslint vs prettier vs stylelint vs tslint.

Similar Npm Packages to prettier

prettier is an opinionated code formatter that helps developers maintain consistent code style across their projects. It automatically formats code according to predefined rules, making it easier to read and reducing the likelihood of style-related issues. While prettier is widely used for code formatting, there are several alternatives that also serve similar purposes. Here are a few notable ones:

  • eslint is primarily a linting tool for JavaScript and JSX code, but it also offers formatting capabilities. With a wide range of rules and plugins, ESLint helps developers identify and fix problems in their code, ensuring adherence to coding standards. While ESLint focuses on code quality and potential errors, it can be configured to format code as well, making it a versatile tool for maintaining code style and quality.
  • js-beautify is a simple and flexible JavaScript code beautifier that can format HTML, CSS, and JavaScript code. It allows developers to customize formatting options according to their preferences. While js-beautify is a straightforward tool for beautifying code, it may not offer the same level of integration and automation as prettier, making it more suitable for quick formatting tasks rather than comprehensive code style enforcement.
  • standard is a JavaScript style guide, linter, and formatter that enforces a specific coding style without the need for configuration. It promotes a set of rules that developers can follow to ensure consistency across their codebases. Standard is particularly appealing for teams that want to adopt a uniform coding style without spending time on configuration, but it may not offer the same flexibility as prettier in terms of customization.

To see how prettier compares with eslint, js-beautify, and standard, check out the comparison: Comparing eslint vs js-beautify vs prettier vs standard.

Similar Npm Packages to stylelint

stylelint is a powerful, modern linter for CSS and its preprocessors, such as SCSS and Less. It helps developers maintain consistent coding styles and catch errors in their stylesheets before they become problematic. By enforcing coding standards and best practices, stylelint improves the quality of CSS code, making it easier to read and maintain. While stylelint is a robust tool for CSS linting, there are other alternatives in the ecosystem that serve different purposes. Here are a few notable alternatives:

  • eslint is a widely-used linter for JavaScript and JSX code. It helps developers identify and fix problems in their JavaScript code by enforcing coding standards and best practices. While eslint is primarily focused on JavaScript, it can be extended to lint other file types, including styles written in CSS-in-JS libraries. If you're looking for a comprehensive solution for linting both JavaScript and CSS-in-JS styles, eslint is a great choice.
  • prettier is an opinionated code formatter that supports multiple languages, including JavaScript, CSS, and HTML. Unlike traditional linters, which focus on identifying potential issues in the code, prettier automatically formats code according to a set of rules. This ensures a consistent code style across your project without requiring manual adjustments. While prettier doesn't replace stylelint, it can be used alongside it to ensure both linting and formatting of CSS and other code types.
  • sass-lint is a linter specifically designed for Sass (Syntactically Awesome Style Sheets). It helps enforce coding standards and best practices in Sass files, similar to what stylelint does for CSS. If your project primarily uses Sass and you want a linter tailored specifically for that preprocessor, sass-lint is a suitable alternative.

To see how stylelint compares with eslint, prettier, and sass-lint, check out the comparison: Comparing eslint vs prettier vs sass-lint vs stylelint.

Similar Npm Packages to tslint

tslint is a static analysis tool for TypeScript code that helps developers identify and fix problems in their codebase. It enforces coding standards and best practices, ensuring that TypeScript code is clean, consistent, and maintainable. While tslint has been widely used in the TypeScript community, it has been deprecated in favor of using eslint with TypeScript support. Here are some alternatives to consider:

  • eslint is a popular static code analysis tool for JavaScript and TypeScript. It provides a robust framework for identifying and fixing problems in code, as well as enforcing coding standards. With the addition of TypeScript support through plugins, eslint has become the go-to choice for many developers looking to maintain high-quality codebases. Its extensive ecosystem of plugins and configurations allows for great flexibility, making it suitable for a wide range of projects.
  • prettier is an opinionated code formatter that focuses on maintaining consistent code style across a project. While it is not a linter in the traditional sense, it can be used alongside linters like eslint to ensure that code is not only free of errors but also formatted consistently. prettier automatically formats code based on predefined rules, which can save developers time and reduce the cognitive load of managing code style manually.
  • stylelint is a modern linter for CSS and other style formats. It helps developers enforce consistent conventions and avoid errors in their stylesheets. While stylelint is not directly related to TypeScript or JavaScript, it is an essential tool for projects that involve CSS or preprocessors like SCSS or LESS. If your project includes a significant amount of styling, integrating stylelint can help maintain high-quality styles.

For a comprehensive comparison of these packages, check out the link: Comparing eslint vs prettier vs stylelint vs tslint.

Similar Npm Packages to jshint

jshint is a static code analysis tool used to detect errors and potential problems in JavaScript code. It helps developers maintain code quality by identifying issues such as syntax errors, coding style violations, and potential bugs. While JSHint has been a popular choice for linting JavaScript code, there are several alternatives available that offer similar or enhanced functionality. Here are a few notable alternatives:

  • eslint is one of the most widely used linting tools for JavaScript. It provides a highly customizable linting experience, allowing developers to define their own rules and configurations. ESLint supports modern JavaScript features and integrates well with various development environments. Its extensive plugin ecosystem enables developers to extend its capabilities further, making it a versatile choice for both small and large projects. If you're looking for a robust and flexible linting solution, ESLint is an excellent option.
  • jscs (JavaScript Code Style) is a linter that focuses specifically on code style issues. It allows developers to enforce coding conventions and style guidelines in their JavaScript code. While it has been somewhat overshadowed by ESLint, which has incorporated many of its features, JSCS can still be useful for projects that prioritize strict adherence to specific coding styles. If your team has established coding standards that you want to enforce, JSCS can help ensure compliance.
  • standard is a JavaScript style guide, linter, and formatter that enforces a set of rules without requiring configuration. It aims to provide a zero-configuration experience, allowing developers to focus on writing code rather than configuring linting rules. Standard is particularly appealing for teams looking for a straightforward and opinionated approach to code style. If you prefer a no-frills solution that enforces consistency without the overhead of configuration, Standard is a great choice.

To see how JSHint compares with ESLint, JSCS, and Standard, check out the comparison: Comparing eslint vs jscs vs jshint vs standard.

Similar Npm Packages to oxlint

oxlint is a modern linting tool designed to help developers maintain code quality and consistency in their JavaScript projects. It provides a flexible and extensible framework for identifying and fixing potential issues in code, ensuring adherence to coding standards and best practices. While oxlint is a great choice for linting, there are several alternatives that developers can consider:

  • eslint is one of the most popular linting tools for JavaScript. It allows developers to define and enforce coding standards through customizable rules. ESLint is highly extensible, with a vast ecosystem of plugins and integrations, making it suitable for various project types. If you're looking for a comprehensive linting solution that supports modern JavaScript features and frameworks, ESLint is an excellent choice.
  • jshint is another JavaScript linting tool that focuses on detecting potential issues in code. While it is less configurable than ESLint, JSHint is straightforward to use and can quickly identify common problems. It is a good option for developers who prefer a simpler linting tool without the need for extensive customization.
  • prettier is a code formatter rather than a traditional linter, but it plays a crucial role in maintaining code quality. Prettier automatically formats code according to defined styles, ensuring consistency across the codebase. While it does not perform linting in the same way as ESLint or oxlint, it can be used in conjunction with linting tools to enhance code quality.
  • stylelint is a powerful linter specifically designed for CSS and other style-related files. It helps developers maintain consistency in their stylesheets by enforcing coding standards and best practices. If your project involves a significant amount of CSS or preprocessor languages like SCSS or LESS, integrating stylelint can greatly improve your styling workflow.
  • tslint was a popular linting tool for TypeScript projects. However, it has been deprecated in favor of ESLint, which now supports TypeScript through plugins. If you're working with TypeScript, using ESLint with the appropriate TypeScript plugin is recommended for linting.

To compare oxlint with these alternatives, check out the following link: Comparing eslint vs jshint vs oxlint vs prettier vs stylelint vs tslint.

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:

import { defineConfig } from "eslint/config";

export default defineConfig([
	{
		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 		루밀LuMir's Avatar
루밀LuMir

Website Team

Team members who focus specifically on eslint.org

Amaresh S M's Avatar
Amaresh S M 		Harish's Avatar
Harish 		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.

Diamond Sponsors

AG Grid

Platinum Sponsors

Automattic Airbnb

Gold Sponsors

Qlty Software trunk.io Shopify

Silver Sponsors

Vite 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

npm-compare.com is an independent website designed to help developers choose the most suitable npm packages. We are not affiliated with npm, Inc or npmjs.com, the official website for the npm registry. Please note that npm is a registered trademark of npm, Inc. For more details, please refer to our Terms & Privacy.