The esbuild vs SWC comparison on OctoCounts shows side-by-side source line counts for evanw/esbuild and swc-project/swc, 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 evanw/esbuild and swc-project/swc 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-09, evanw/esbuild contains 251,847 total lines (171,984 code) across 323 files, while swc-project/swc contains 1,991,549 total lines (1,619,644 code) across 1,928 files as of 2026-11-16. swc-project/swc has about 9.4x the counted code lines of evanw/esbuild 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.
| Metric | evanw/esbuild | swc-project/swc |
|---|---|---|
| Files | 323 | 1,928 |
| Total lines | 251,847 | 1,991,549 |
| Code lines | 171,984 | 1,619,644 |
| Comment lines | 53,980 | 191,056 |
| Blank lines | 25,883 | 180,849 |
| Languages counted | 11 | 13 |
Top languages in evanw/esbuild: Go (70.1% of code), JavaScript (17.2% of code), JSON (6.7% of code). Top languages in swc-project/swc: JavaScript (43.4% of code), TypeScript (27.3% of code), Rust (20.5% of code). JavaScript, JSON, TypeScript appear in both top language lists; Go, Makefile appear only in evanw/esbuild's top languages; Rust, TSX appear only in swc-project/swc's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. evanw/esbuild was counted at ref main (commit f6058f8364fe) on 2026-11-09; swc-project/swc was counted at ref main (commit 06ee4346efa5) on 2026-11-16. 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. evanw/esbuild: 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. swc-project/swc: 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.
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: evanw/esbuild is the esbuild repository: a bundler, minifier, and JavaScript/TypeScript toolchain written in Go. swc-project/swc is the SWC repository: a compiler and toolchain written in Rust, with its JavaScript/TypeScript packages alongside the native core. Both are single-purpose build-tool repositories with their tests and bindings in-tree, counted on the dates above.
Each per-language table reduces to essentially one row: esbuild's counted code is Go, and SWC's counted code is predominantly Rust, so the totals read directly as the size of each single-language toolchain implementation.
Repository size here says nothing about build speed or output size: both tools advertise native-code performance, which is a property of the shipped binaries and the code they process, not of the source line counts on this page.
Sources: evanw/esbuild repository (Go toolchain) · swc-project/swc repository (Rust core with TypeScript/JavaScript packages). 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.
As of 2026-11-09, evanw/esbuild contains 251,847 total lines (171,984 code) across 323 files, while swc-project/swc contains 1,991,549 total lines (1,619,644 code) across 1,928 files as of 2026-11-16. swc-project/swc has about 9.4x the counted code lines of evanw/esbuild 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.
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 evanw/esbuild, swc-project/swc, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. evanw/esbuild was counted at ref main (commit f6058f8364fe) on 2026-11-09; swc-project/swc was counted at ref main (commit 06ee4346efa5) on 2026-11-16. See the counting methodology for ignored directories and analysis options.
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.