This page compares the source lines of code (SLOC) of nuxt/nuxt and vercel/next.js 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-08-26, nuxt/nuxt contains 79,792 total lines (61,042 code) across 541 files, while vercel/next.js contains 888,801 total lines (717,794 code) across 8,045 files as of 2026-09-08. vercel/next.js is about 12x the size of nuxt/nuxt by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | nuxt/nuxt | vercel/next.js |
|---|---|---|
| Files | 541 | 8,045 |
| Total lines | 79,792 | 888,801 |
| Code lines | 61,042 | 717,794 |
| Comment lines | 9,204 | 82,809 |
| Blank lines | 9,546 | 88,198 |
| Languages counted | 10 | 12 |
Top languages in nuxt/nuxt: TypeScript (69.5% of code), YAML (26.4% of code), JSON (2.3% of code). Top languages in vercel/next.js: Rust (33.7% of code), TypeScript (30.4% of code), TSX (11.1% of code). TypeScript, JSON, JavaScript appear in both top language lists; YAML, SVG appear only in nuxt/nuxt's top languages; Rust, TSX appear only in vercel/next.js's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. nuxt/nuxt was counted at ref main (commit e0deb2cd13fe) on 2026-08-26; vercel/next.js was counted at ref canary (commit 969733cfb701) on 2026-09-08. 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.
vercel/next.js has more code: 717,794 code lines versus 61,042 for nuxt/nuxt, about 12x 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 nuxt/nuxt, vercel/next.js, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. nuxt/nuxt was counted at ref main (commit e0deb2cd13fe) on 2026-08-26; vercel/next.js was counted at ref canary (commit 969733cfb701) 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.