# Prettier vs ESLint: source lines of code compared

The Prettier vs ESLint comparison on OctoCounts shows side-by-side source line counts for prettier/prettier and eslint/eslint, counted with the same engine and analysis options on the dates shown in the methodology line: files, total lines, code lines, comment lines, blank lines, and per-language totals, pinned to the exact commits listed below.

As of 2026-09-21, prettier/prettier contains 101,586 total lines (51,752 code) across 876 files, while eslint/eslint contains 122,493 total lines (71,307 code) across 465 files as of 2026-09-16. eslint/eslint is about 1.4x the size of prettier/prettier by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.

| Metric | [prettier/prettier](https://octocounts.com/github/prettier/prettier) | [eslint/eslint](https://octocounts.com/github/eslint/eslint) |
| --- | ---: | ---: |
| Files | 876 | 465 |
| Total lines | 101,586 | 122,493 |
| Code lines | 51,752 | 71,307 |
| Comment lines | 33,022 | 37,734 |
| Blank lines | 16,812 | 13,452 |
| Languages counted | 12 | 5 |

Top languages in prettier/prettier: JavaScript (87.2% of code), TypeScript (5.2% of code), JSX (3.3% of code). Top languages in eslint/eslint: JavaScript (94.4% of code), TypeScript (4.9% of code), JSON (0.7% of code). JavaScript, TypeScript, JSON appear in both top language lists; JSX, CSS appear only in prettier/prettier's top languages; Shell, Markdown appear only in eslint/eslint's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. prettier/prettier was counted at ref main (commit 51ed2cbbf3b4) on 2026-09-21; eslint/eslint was counted at ref 28cc7abbb72b29b1cac6fc4253646a7839586064 (commit 28cc7abbb72b) on 2026-09-16. See the [counting methodology](https://octocounts.com/docs/methodology) for ignored directories and analysis options.
## About this comparison

prettier/prettier counts the Prettier repository — the opinionated code formatter and its bundled language support — while eslint/eslint counts the ESLint core linter; ESLint's large rule/plugin ecosystem mostly lives in separate repositories, as do Prettier's standalone plugins. The counts are therefore comparable as core-tooling source trees, taken on the dates shown in the methodology line.

Both repositories are implemented predominantly in JavaScript, per the per-language tables; the contrast on the page is one of codebase size, not of implementation approach.

Prettier's repository carries a substantial share of formatter support for many languages, while ESLint's core is scoped to JavaScript-family linting with an extension API — so part of the size difference reflects how much language coverage each core chooses to own.

_Formatter and linter are complementary, not competing, tools: ESLint flags patterns against rules, Prettier rewrites formatting. These counts cannot rank them, and many projects use both together._

Sources: [prettier/prettier repository](https://github.com/prettier/prettier) · [eslint/eslint repository](https://github.com/eslint/eslint). Statements verified 2026-09-16.

Evidence and next steps:

- [prettier/prettier SLOC report](https://octocounts.com/github/prettier/prettier)
- [eslint/eslint SLOC report](https://octocounts.com/github/eslint/eslint)
- [Compare prettier/prettier and eslint/eslint interactively](https://octocounts.com/compare?left=https%3A%2F%2Fgithub.com%2Fprettier%2Fprettier&right=https%3A%2F%2Fgithub.com%2Feslint%2Feslint)

Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.

## Compare FAQ

### Which has more lines of code, prettier/prettier or eslint/eslint?

eslint/eslint has more code: 71,307 code lines versus 51,752 for prettier/prettier, about 1.4x as much, based on cached OctoCounts reports as of 2026-09-21.

### Does more source lines of code mean more complexity?

Not necessarily. SLOC measures size, not complexity, quality, or maintainability. A larger codebase can mean more features, more generated or vendored code, more verbose language idioms, or more tests — none of which imply the code is harder to work with. Use SLOC to gauge the scale of what you'd be reading or maintaining, not as a quality signal for prettier/prettier, eslint/eslint, or any repository.

### How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. prettier/prettier was counted at ref main (commit 51ed2cbbf3b4) on 2026-09-21; eslint/eslint was counted at ref 28cc7abbb72b29b1cac6fc4253646a7839586064 (commit 28cc7abbb72b) on 2026-09-16. See the counting methodology for ignored directories and analysis options.

### Can I compare a different branch, tag, or commit?

Yes. This page shows the default branch for each repository. Use the interactive comparison tool to pick any public GitHub repository, branch, tag, or commit SHA for both sides and get a fresh side-by-side report.

## Related OctoCounts pages

- [Interactive repository comparison](https://octocounts.com/compare)
- [Recently analyzed repositories](https://octocounts.com/recent)
- [Popular SLOC reports](https://octocounts.com/popular)
- [Trending GitHub repositories](https://octocounts.com/trending)
- [Hall of Monoliths](https://octocounts.com/hall-of-monoliths)
- [Original research: how filtering changes SLOC counts](https://octocounts.com/research)
- [GitHub SLOC counter guide](https://octocounts.com/docs/github-sloc-counter)
- [Counting methodology](https://octocounts.com/docs/methodology)
- [SLOC and code metrics glossary](https://octocounts.com/docs/glossary)
- [OctoCounts API docs](https://octocounts.com/docs/api)