Prettier vs ESLint: source lines of code compared

This page compares the source lines of code (SLOC) of prettier/prettier and eslint/eslint using cached OctoCounts reports. Code size is not code quality: a larger count only means more source material, not a better or worse project.

As of 2026-08-31, prettier/prettier contains 100,806 total lines (51,319 code) across 861 files, while eslint/eslint contains 124,114 total lines (71,872 code) across 473 files as of 2026-09-07. 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.

Metricprettier/prettiereslint/eslint
Files861473
Total lines100,806124,114
Code lines51,31971,872
Comment lines32,81638,600
Blank lines16,67113,642
Languages counted125

Top languages in prettier/prettier: JavaScript (87.1% of code), TypeScript (5.3% of code), JSX (3.3% of code). Top languages in eslint/eslint: JavaScript (94.9% of code), TypeScript (4.2% of code), JSON (0.9% 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 5fd5b6908b8d) on 2026-08-31; eslint/eslint was counted at ref main (commit c8326608e710) on 2026-09-07. See the counting methodology for ignored directories and analysis options.

Evidence and next steps:

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,872 code lines versus 51,319 for prettier/prettier, about 1.4x as much, based on cached OctoCounts reports as of 2026-09-07.

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 5fd5b6908b8d) on 2026-08-31; eslint/eslint was counted at ref main (commit c8326608e710) on 2026-09-07. 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.