prettier/prettier-eslint

Code :arrow_right: `prettier` :arrow_right: `eslint --fix` :arrow_right: Formatted Code :sparkles:

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 25 minutes ago
Type:Library / SDKCategory(s):Code Quality & Static AnalysisDeveloper Tools
Added to GitGenius on September 16th, 2026
Created on January 13th, 2017
Open Issues & Pull Requests: 3 (+0)
GitHub issues: Enabled
Number of forks: 171
Total Stargazers: 4,101 (+0)
Total Subscribers: 26 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.5 hours
Mean response time: 171.9 days
90th percentile: 87.2 days
Tracked items: 12

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 541 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

  • no-issue-activity (4)
  • PR welcome (2)
  • enhancement (2)
  • feature (2)
  • help wanted (2)
  • dependencies (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

prettier-eslint is a code formatter that integrates Prettier and ESLint by running code through Prettier first, then through ESLint's fix mode to resolve any remaining linting issues.

The tool solves the problem of conflicts between Prettier's formatting rules and ESLint's linting rules. When developers use both tools together, they can produce contradictory outputs that require manual resolution. prettier-eslint addresses this by chaining the two tools in sequence: code is formatted by Prettier, and then ESLint's automatic fixing pass resolves any style violations that Prettier may have introduced, producing output that satisfies both formatters.

Developers should choose this tool if they maintain a codebase that relies on both Prettier for code formatting and ESLint for linting, and want to avoid the friction of conflicting rules between the two. It suits projects where the team has invested in configuring both tools and wants a unified formatting pipeline. The tool is particularly useful in editor integrations and CI/CD workflows where a single formatting command needs to produce code that passes both Prettier and ESLint checks without manual intervention.

The project shows consistent maintenance with regular commits addressing bug fixes and dependency updates. Pull requests are reviewed and merged steadily, indicating active engagement with contributions. Issues are addressed with responses from maintainers, though resolution timelines vary. The codebase receives updates to keep pace with changes in its dependencies, particularly Prettier and ESLint themselves. Documentation is maintained to reflect the tool's usage and configuration options.