prettier/eslint-plugin-prettier

ESLint plugin for Prettier formatting

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 3 minutes ago
Type:Plugin / ExtensionCategory(s):Code Quality & Static AnalysisDeveloper Tools
Added to GitGenius on September 19th, 2026
Created on January 26th, 2017
Open Issues & Pull Requests: 22 (+0)
GitHub issues: Enabled
Number of forks: 212
Total Stargazers: 3,653 (+0)
Total Subscribers: 16 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.3 hours
Mean response time: 20.3 days
90th percentile: 47.8 days
Tracked items: 46

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 10
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 677 days
Stale 30+ days: 8
Stale 90+ days: 6

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • question (11)
  • good first issue (3)
  • internal (3)
  • upstream (3)
  • bug (1)
  • ci (1)
  • invalid (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

eslint-plugin-prettier is an ESLint plugin that runs Prettier as an ESLint rule and reports formatting differences as individual linting issues.

The plugin solves the problem of integrating code formatting checks into your linting workflow. Rather than running Prettier as a separate tool, it embeds Prettier's formatting logic directly into ESLint, allowing formatting violations to surface alongside other linting problems. This approach works by executing Prettier on your code and comparing its output to what you've written, then reporting any mismatches as ESLint violations that can be automatically fixed.

You should adopt this tool if you want formatting enforcement integrated into your existing ESLint setup. It works best in projects where you've disabled all other ESLint formatting rules and rely solely on Prettier for code style, using ESLint only for bug detection. The README explicitly cautions that if your desired formatting does not match Prettier's output, you should use a different tool such as prettier-eslint instead. The plugin ships with a recommended configuration that automatically disables conflicting ESLint rules and enables eslint-config-prettier to prevent rule conflicts. It supports both legacy .eslintrc configuration files and the newer flat eslint.config.js format, and includes Svelte support.

The project maintains active continuous integration with a build status pipeline. Development follows a structured changelog and contribution process with documented guidelines for contributors.