This page compares the source lines of code (SLOC) of vercel/next.js and vitejs/vite 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-09-08, vercel/next.js contains 888,801 total lines (717,794 code) across 8,045 files, while vitejs/vite contains 154,394 total lines (112,297 code) across 2,584 files as of 2026-09-08. vercel/next.js is about 6.4x the size of vitejs/vite by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | vercel/next.js | vitejs/vite |
|---|---|---|
| Files | 8,045 | 2,584 |
| Total lines | 888,801 | 154,394 |
| Code lines | 717,794 | 112,297 |
| Comment lines | 82,809 | 22,939 |
| Blank lines | 88,198 | 19,158 |
| Languages counted | 12 | 12 |
Top languages in vercel/next.js: Rust (33.7% of code), TypeScript (30.4% of code), TSX (11.1% of code). Top languages in vitejs/vite: TypeScript (67.7% of code), YAML (10.5% of code), JavaScript (8.7% of code). TypeScript, JSON, JavaScript appear in both top language lists; Rust, TSX appear only in vercel/next.js's top languages; YAML, CSS appear only in vitejs/vite's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. vercel/next.js was counted at ref canary (commit 969733cfb701) on 2026-09-08; vitejs/vite was counted at ref e6f6b3e3119256daa837b2dc399058c8aa45b470 (commit e6f6b3e31192) on 2026-09-08. See the counting methodology for ignored directories and analysis options.
vercel/next.js counts the Next.js monorepo — the framework packages, examples, documentation site, and test suites — while vitejs/vite counts the Vite core repository only. The comparison is framework-repository vs build-tool-repository: related layers of the stack, but not the same kind of software, and the counts were taken on the dates shown above.
Next.js's count includes documentation-site content and a large examples directory as part of its monorepo, so a substantial part of what is counted exists to teach and demonstrate rather than to ship as framework code.
The two counts describe different layers: Next.js is a framework that orchestrates rendering, routing, and data loading (and uses build tooling underneath), while Vite is that build tooling layer. Reading the numbers side by side is most useful as a sense of each project's reading and maintenance surface.
This is not a framework-vs-build-tool performance or popularity comparison. Source-tree size says nothing about which to choose; the decision depends on the application's rendering and build requirements.
Sources: vercel/next.js repository structure (monorepo with examples and docs) · vitejs/vite repository. Statements verified 2026-09-08.
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.
vercel/next.js has more code: 717,794 code lines versus 112,297 for vitejs/vite, about 6.4x as much, based on cached OctoCounts reports as of 2026-09-08.
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 vercel/next.js, vitejs/vite, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. vercel/next.js was counted at ref canary (commit 969733cfb701) on 2026-09-08; vitejs/vite was counted at ref e6f6b3e3119256daa837b2dc399058c8aa45b470 (commit e6f6b3e31192) on 2026-09-08. 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.