SolidJS vs React: source lines of code compared

The SolidJS vs React comparison on OctoCounts shows side-by-side source line counts for solidjs/solid and react/react, 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 solidjs/solid and react/react 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-13, solidjs/solid contains 25,707 total lines (17,321 code) across 133 files, while react/react contains 459,535 total lines (364,650 code) across 2,112 files as of 2026-11-12. react/react has about 21x the counted code lines of solidjs/solid 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.

Metricsolidjs/solidreact/react
Files1332,112
Total lines25,707459,535
Code lines17,321364,650
Comment lines4,55458,728
Blank lines3,83236,157
Languages counted711

Top languages in solidjs/solid: JavaScript (33.5% of code), YAML (31.5% of code), TypeScript (29.8% of code). Top languages in react/react: JavaScript (63.1% of code), Rust (17.8% of code), TypeScript (16.6% of code). JavaScript, TypeScript, JSON, CSS appear in both top language lists; YAML appears only in solidjs/solid's top languages; Rust appears only in react/react's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. solidjs/solid was counted at ref main (commit e2a181dc4e51) on 2026-11-13; react/react was counted at ref main (commit df6aa4ec76cf) on 2026-11-12. 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. solidjs/solid: 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. react/react: 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-10-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: solidjs/solid is the Solid repository: the reactive runtime, the JSX transform/compiler packages, and supporting packages in a monorepo, with tests and documentation. react/react is the React monorepo: the React packages plus fixtures, documentation site content, and test infrastructure. Both repositories are framework source trees, not applications built with them, and both were counted on the dates shown above.

The two runtimes are organized around different update models — Solid around fine-grained reactive primitives, React around a scheduler-driven runtime — an architectural difference the counts themselves cannot express, so the totals are best read as maintenance surface.

Repository size does not predict the bundle size shipped to a browser or runtime behavior; a compiled application contains only the parts of the framework it actually uses.

Sources: solidjs/solid repository · react/react repository structure (packages/ monorepo). Statements verified 2026-10-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, solidjs/solid or react/react?

As of 2026-11-13, solidjs/solid contains 25,707 total lines (17,321 code) across 133 files, while react/react contains 459,535 total lines (364,650 code) across 2,112 files as of 2026-11-12. react/react has about 21x the counted code lines of solidjs/solid 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 solidjs/solid, react/react, or any repository.

How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. solidjs/solid was counted at ref main (commit e2a181dc4e51) on 2026-11-13; react/react was counted at ref main (commit df6aa4ec76cf) on 2026-11-12. 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.