Biome vs Prettier: source lines of code compared

The Biome vs Prettier comparison on OctoCounts shows side-by-side source line counts for biomejs/biome and prettier/prettier, 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 biomejs/biome and prettier/prettier 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-16, biomejs/biome contains 1,048,535 total lines (880,726 code) across 5,539 files, while prettier/prettier contains 103,657 total lines (52,652 code) across 855 files as of 2026-11-14. biomejs/biome has about 17x 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.

Metricbiomejs/biomeprettier/prettier
Files5,539855
Total lines1,048,535103,657
Code lines880,72652,652
Comment lines70,06333,788
Blank lines97,74617,217
Languages counted1113

Top languages in biomejs/biome: Rust (86.8% of code), JSON (6.5% of code), TypeScript (4.9% of code). Top languages in prettier/prettier: JavaScript (87.0% of code), TypeScript (5.6% of code), JSX (3.2% of code). JSON, TypeScript, JavaScript appear in both top language lists; Rust, TOML appear only in biomejs/biome's top languages; JSX, CSS appear only in prettier/prettier's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. biomejs/biome was counted at ref main (commit 1fef1e2c8621) on 2026-11-16; prettier/prettier was counted at ref main (commit 2cc4f0fd2cc4) on 2026-11-14. 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. biomejs/biome: 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. 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.

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: biomejs/biome is the Biome repository: an all-in-one toolchain whose formatter and linter live in a single Rust codebase. prettier/prettier is the Prettier repository: the standalone code formatter written in JavaScript. The comparison is a multi-tool repository against a single-purpose formatter, and both repositories were taken on the dates in the methodology line.

The language tables identify each project's implementation language at a glance: Biome's counted code is predominantly Rust, while Prettier's is JavaScript — different systems languages for tools that overlap in the formatting role.

Biome's repository covers both formatting and linting, so part of its count exists for linter functionality that has no counterpart in the Prettier repository, which is formatter-only.

Repository size does not measure formatting speed or result quality; both properties depend on the shipped tool version and the languages being formatted, not on the source tree's line count.

Sources: biomejs/biome repository · prettier/prettier 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, biomejs/biome or prettier/prettier?

As of 2026-11-16, biomejs/biome contains 1,048,535 total lines (880,726 code) across 5,539 files, while prettier/prettier contains 103,657 total lines (52,652 code) across 855 files as of 2026-11-14. biomejs/biome has about 17x 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 biomejs/biome, prettier/prettier, or any repository.

How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. biomejs/biome was counted at ref main (commit 1fef1e2c8621) on 2026-11-16; prettier/prettier was counted at ref main (commit 2cc4f0fd2cc4) on 2026-11-14. 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.