eslint vs prettier vs stylelint vs tslint
JavaScript ve CSS Kod Kalite Araçları
eslintprettierstylelinttslintBenzer Paketler:

JavaScript ve CSS Kod Kalite Araçları

Bu araçlar, JavaScript ve CSS kodunun kalitesini artırmak, hataları önlemek ve kodun tutarlılığını sağlamak için kullanılır. Her biri farklı bir amaca hizmet eder ve geliştiricilerin kod yazma süreçlerini daha verimli hale getirir. ESLint, JavaScript kodu için statik analiz yaparken, Prettier kod biçimlendirme aracı olarak işlev görür. Stylelint, CSS ve stil dosyaları için bir linter iken, TSLint TypeScript için benzer bir işlev sunar. Bu araçlar, kodun okunabilirliğini artırır ve geliştirme sürecinde hata oranını azaltır.

npm İndirme Trendi

3 Yıl

GitHub Stars Sıralaması

İstatistik Detayı

Paket
İndirmeler
Stars
Boyut
Issues
Yayın Tarihi
Lisans
eslint027,6022.95 MB130il y a un jourMIT
prettier052,3909.96 MB1,475il y a 22 joursMIT
stylelint011,541987 kB108il y a un moisMIT
tslint05,892-1il y a 6 ansApache-2.0

Özellik Karşılaştırması: eslint vs prettier vs stylelint vs tslint

Kod Analizi

  • eslint:

    ESLint, JavaScript kodunu analiz ederek hataları ve potansiyel sorunları tespit eder. Geliştiricilere, kod yazarken anında geri bildirim sağlayarak hataların erken aşamada düzeltilmesine yardımcı olur.

  • prettier:

    Prettier, kodun biçimlendirilmesiyle ilgilenir ve belirli kurallara göre kodu otomatik olarak düzenler. Bu, kodun okunabilirliğini artırır ve geliştiricilerin farklı biçimlendirme stilleri arasında kaybolmalarını önler.

  • stylelint:

    Stylelint, CSS ve stil dosyalarını analiz ederek hataları ve tutarsızlıkları tespit eder. Geliştiricilere, stil dosyalarında daha temiz ve tutarlı bir yapı sağlamalarına yardımcı olur.

  • tslint:

    TSLint, TypeScript kodunu analiz eder ve hataları tespit eder. Ancak, TypeScript topluluğu artık TSLint yerine ESLint'i önerdiği için, yeni projelerde ESLint kullanmak daha mantıklıdır.

Biçimlendirme

  • eslint:

    ESLint, kodun biçimlendirilmesiyle ilgili bazı kurallar sunar, ancak esas olarak kod kalitesine odaklanır. Biçimlendirme için Prettier ile birlikte kullanılabilir.

  • prettier:

    Prettier, kodu otomatik olarak biçimlendirir ve belirli bir stil standardına göre düzenler. Bu, tüm proje boyunca tutarlılığı sağlar ve geliştiricilerin biçimlendirme ile ilgili tartışmalara zaman harcamalarını önler.

  • stylelint:

    Stylelint, CSS stil dosyalarının biçimlendirilmesiyle ilgili kurallar belirleyebilir. Bu, stil dosyalarının okunabilirliğini artırır ve tutarlılığı sağlar.

  • tslint:

    TSLint, TypeScript kodunun biçimlendirilmesine dair bazı kurallar sunar, ancak esas olarak kod kalitesine odaklanır. Biçimlendirme için Prettier ile birlikte kullanılabilir.

Kuralların Özelleştirilmesi

  • eslint:

    ESLint, geliştiricilerin kendi kurallarını tanımlamalarına ve mevcut kuralları özelleştirmelerine olanak tanır. Bu, projeye özgü gereksinimlere göre ayarlamalar yapmayı kolaylaştırır.

  • prettier:

    Prettier, sınırlı özelleştirme seçenekleri sunar, çünkü amacı kodu tutarlı bir şekilde biçimlendirmektir. Ancak, bazı ayarlarla belirli stiller üzerinde kontrol sağlar.

  • stylelint:

    Stylelint, geliştiricilerin kendi kurallarını tanımlamalarına ve mevcut kuralları özelleştirmelerine olanak tanır. Bu, stil dosyalarının projenin gereksinimlerine göre ayarlanmasını sağlar.

  • tslint:

    TSLint, özelleştirilebilir kurallar sunar, ancak TypeScript topluluğu artık ESLint'i önerdiği için yeni projelerde ESLint kullanmak daha mantıklıdır.

Topluluk Desteği

  • eslint:

    ESLint, geniş bir topluluk desteğine sahiptir ve birçok popüler kütüphane ve çerçeve ile entegrasyon sağlar. Bu, sorunların hızlı bir şekilde çözülmesini ve yeni özelliklerin eklenmesini kolaylaştırır.

  • prettier:

    Prettier, geniş bir kullanıcı tabanına ve topluluk desteğine sahiptir. Bu, sürekli güncellemeler ve yeni özelliklerin eklenmesi anlamına gelir.

  • stylelint:

    Stylelint, CSS topluluğunda yaygın olarak kullanılmaktadır ve geniş bir eklenti ekosistemine sahiptir. Bu, geliştiricilere ek işlevsellik sağlar.

  • tslint:

    TSLint, geçmişte popülerdi ancak artık topluluk desteği azalmaktadır. TypeScript topluluğu, ESLint'e geçiş yapmayı önerdiği için yeni projelerde ESLint kullanmak daha mantıklıdır.

Entegrasyon Kolaylığı

  • eslint:

    ESLint, birçok geliştirme ortamı ve araç ile kolayca entegre edilebilir. Bu, geliştiricilerin mevcut iş akışlarına sorunsuz bir şekilde dahil etmelerini sağlar.

  • prettier:

    Prettier, çeşitli IDE ve metin editörleri ile entegre edilebilir. Bu, geliştiricilerin kod yazarken otomatik biçimlendirme yapmalarını sağlar.

  • stylelint:

    Stylelint, popüler CSS araçları ve çerçeveleri ile entegre edilebilir. Bu, stil dosyalarının denetlenmesini kolaylaştırır.

  • tslint:

    TSLint, bazı geliştirme ortamları ile entegre edilebilir, ancak topluluk desteği azaldığı için yeni projelerde ESLint kullanmak daha mantıklıdır.

Nasıl Seçilir: eslint vs prettier vs stylelint vs tslint

  • eslint:

    JavaScript projelerinizde kod kalitesini artırmak ve hataları önlemek istiyorsanız ESLint'i tercih edin. Özellikle büyük projelerde, kurallarınızı özelleştirerek takım içinde tutarlılığı sağlamak için idealdir.

  • prettier:

    Kodunuzun biçimlendirilmesi konusunda tutarlılık sağlamak istiyorsanız Prettier'i seçin. Prettier, kodunuzu otomatik olarak biçimlendirerek, geliştiricilerin stil tartışmalarına zaman harcamadan odaklanmalarını sağlar.

  • stylelint:

    CSS ve stil dosyalarınızı denetlemek ve hataları önlemek istiyorsanız Stylelint'i kullanın. Özellikle büyük stil dosyalarında tutarlılık sağlamak için mükemmel bir araçtır.

  • tslint:

    TypeScript projeleri için özel bir linter arıyorsanız TSLint'i tercih edin. Ancak, TypeScript topluluğu ESLint'e geçiş yapmayı önerdiği için yeni projelerde ESLint kullanmanız daha iyi olabilir.

eslint için README

npm version Downloads Build Status
Open Collective Backers Open Collective Sponsors

ESLint

Website | Configure ESLint | Rules | Contribute to ESLint | Report Bugs | Code of Conduct | X | 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. ESM Dependencies
  11. License
  12. Team
  13. Sponsors
  14. Technology Sponsors

Installation and Usage

Prerequisites

To use ESLint, you must have Node.js (^20.19.0, ^22.13.0, or >=24) installed and built with SSL and ICU support. (If you are using an official Node.js distribution, both SSL and ICU are always built in.)

If you use ESLint's TypeScript type definitions, TypeScript 5.3 or later is required.

npm Installation

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 previous versions through our partner, 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 that results in ESLint reporting more linting errors (e.g., fixing false negatives in a core rule, or linting additional files that were previously incorrectly skipped).
    • 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.

ESM Dependencies

Since ESLint is a CommonJS package, there are restrictions on which ESM-only packages can be used as dependencies.

Packages that are controlled by the ESLint team and have no external dependencies can be safely loaded synchronously using require(esm) and therefore used in any contexts.

For external packages, we don't use require(esm) because a package could add a top-level await and thus break ESLint. We can use an external ESM-only package only in case it is needed only in asynchronous code, in which case it can be loaded using dynamic import().

These policies don't apply to packages intended for our own usage only, such as eslint-config-eslint.

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.

fnx's Avatar
fnx
Sweta Tanwar's Avatar
Sweta Tanwar
Tanuj Kanti's Avatar
Tanuj Kanti
lumir's Avatar
lumir
Pixel's Avatar
Pixel

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.

Gold Sponsors

Vite Ecosystem Fund Qlty Software Shopify CodeRabbit Automattic

Silver Sponsors

Vite Liftoff StackBlitz

Bronze Sponsors

Cybozu SAP Discord GitBook Citadel AI TestMu AI Open Source Office (Formerly 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