Next.js vs Vite: source lines of code compared
As of 2026-08-14, vercel/next.js contains 877,662 total lines (709,246 code) across 8,017 files, while vitejs/vite contains 105,412 total lines (81,768 code) across 1,992 files as of 2026-08-13. vercel/next.js is about 8.7x 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,017 | 1,992 |
| Total lines | 877,662 | 105,412 |
| Code lines | 709,246 | 81,768 |
| Comment lines | 81,514 | 12,959 |
| Blank lines | 86,902 | 10,685 |
| Languages counted | 12 | 12 |
Top languages in vercel/next.js: Rust (32.8% of code), TypeScript (30.6% of code), TSX (11.2% of code). Top languages in vitejs/vite: TypeScript (56.5% of code), YAML (16.2% of code), JavaScript (10.9% 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 0f36a7df8824) on 2026-08-14; vitejs/vite was counted at ref main (commit dcf88bd2ad2b) on 2026-08-13. See the counting methodology for ignored directories and analysis options.
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.