The Nuxt vs Next.js comparison on OctoCounts shows side-by-side source line counts for nuxt/nuxt and vercel/next.js, 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 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-11-16, nuxt/nuxt contains 110,631 total lines (86,820 code) across 712 files, while vercel/next.js contains 1,001,292 total lines (810,912 code) across 8,670 files as of 2026-11-16. vercel/next.js has about 9.3x the counted code lines of nuxt/nuxt 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 | nuxt/nuxt | vercel/next.js |
|---|---|---|
| Files | 712 | 8,670 |
| Total lines | 110,631 | 1,001,292 |
| Code lines | 86,820 | 810,912 |
| Comment lines | 13,918 | 92,894 |
| Blank lines | 9,893 | 97,486 |
| Languages counted | 9 | 29 |
Top languages in nuxt/nuxt: TypeScript (70.2% of code), YAML (26.7% of code), JSON (1.9% of code). Top languages in vercel/next.js: Rust (35.7% of code), TypeScript (30.4% of code), TSX (10.8% of code). TypeScript, JSON, JavaScript appear in both top language lists; YAML, HTML 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 238d65ff04a4) on 2026-11-16; vercel/next.js was counted at ref canary (commit a19c4f99adc8) 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. nuxt/nuxt: 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. vercel/next.js: 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: nuxt/nuxt is the Nuxt monorepo — the Vue-based full-stack framework packages along with their documentation and example material — while vercel/next.js is the Next.js monorepo, the React-based full-stack framework with its own docs, examples, and test suites. Both repositories are framework monorepos of the same architectural role, counted with the rules shown above, which makes this one of the more like-for-like comparisons on this site.
The per-language tables show both repositories are TypeScript-led codebases, matching how each framework presents its public APIs — the difference on the page is in tree size and composition, not in implementation language.
Framework repository size does not predict application bundle size, rendering performance, or hosting cost: a deployed site includes only a compiled subset of the framework plus application code and dependencies.
Sources: nuxt/nuxt repository structure (framework monorepo) · vercel/next.js repository structure (monorepo with examples and docs). 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-16, nuxt/nuxt contains 110,631 total lines (86,820 code) across 712 files, while vercel/next.js contains 1,001,292 total lines (810,912 code) across 8,670 files as of 2026-11-16. vercel/next.js has about 9.3x the counted code lines of nuxt/nuxt 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 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 238d65ff04a4) on 2026-11-16; vercel/next.js was counted at ref canary (commit a19c4f99adc8) 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.