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 under the rules and on the dates stated below: files, total lines, code lines, comment lines, blank lines, and per-language totals, pinned to the exact commits listed below.

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-11-14, prettier/prettier contains 103,657 total lines (52,652 code) across 855 files, while eslint/eslint contains 125,272 total lines (72,350 code) across 475 files as of 2026-11-15. eslint/eslint has about 1.4x the counted code lines of prettier/prettier under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.

Metricprettier/prettiereslint/eslint
Files855475
Total lines103,657125,272
Code lines52,65272,350
Comment lines33,78839,115
Blank lines17,21713,807
Languages counted135

Top languages in prettier/prettier: JavaScript (87.0% of code), TypeScript (5.6% of code), JSX (3.2% of code). Top languages in eslint/eslint: JavaScript (95.0% 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 2cc4f0fd2cc4) on 2026-11-14; eslint/eslint was counted at ref main (commit 97efadd5eff8) on 2026-11-15. See the counting methodology for ignored directories and analysis options.

Both reports use the same engine and effective counting rules. Repository declarations, when enabled, are specific to each repository. prettier/prettier: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed. eslint/eslint: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed.

About this comparison

Background observations recorded on 2026-09-16; language descriptions here are historical context, not claims about the current filtered shares. Use this page's measured language breakdown for current counts. Repository layout before counting filters: prettier/prettier is the Prettier repository — the opinionated code formatter and its bundled language support — while eslint/eslint is the ESLint core linter; ESLint's large rule/plugin ecosystem mostly lives in separate repositories, as do Prettier's standalone plugins. The contains 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 · eslint/eslint repository. Statements verified 2026-09-16.

Evidence and next steps:

Saved reports remain subject to cache cleanup and replacement. Export their JSON for durable citation; live report URLs can change.

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?

As of 2026-11-14, prettier/prettier contains 103,657 total lines (52,652 code) across 855 files, while eslint/eslint contains 125,272 total lines (72,350 code) across 475 files as of 2026-11-15. eslint/eslint has about 1.4x the counted code lines of prettier/prettier under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.

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 2cc4f0fd2cc4) on 2026-11-14; eslint/eslint was counted at ref main (commit 97efadd5eff8) on 2026-11-15. 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.