# Next.js vs React Router: source lines of code compared

The Next.js vs React Router comparison on OctoCounts shows side-by-side source line counts for vercel/next.js and remix-run/react-router, counted with the same engine and analysis options on the dates shown in the methodology line: files, total lines, code lines, comment lines, blank lines, and per-language totals, pinned to the exact commits listed below.

As of 2026-09-21, vercel/next.js contains 910,832 total lines (735,550 code) across 8,331 files, while remix-run/react-router contains 148,256 total lines (104,792 code) across 689 files as of 2026-09-21. vercel/next.js is about 7.0x the size of remix-run/react-router 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](https://octocounts.com/github/vercel/next.js) | [remix-run/react-router](https://octocounts.com/github/remix-run/react-router) |
| --- | ---: | ---: |
| Files | 8,331 | 689 |
| Total lines | 910,832 | 148,256 |
| Code lines | 735,550 | 104,792 |
| Comment lines | 85,162 | 24,801 |
| Blank lines | 90,120 | 18,663 |
| Languages counted | 12 | 12 |

Top languages in vercel/next.js: Rust (33.5% of code), TypeScript (30.6% of code), TSX (11.3% of code). Top languages in remix-run/react-router: TypeScript (72.7% of code), YAML (14.1% of code), TSX (9.5% of code). TypeScript, TSX, JSON, JavaScript appear in both top language lists; Rust appears only in vercel/next.js's top languages; YAML appears only in remix-run/react-router's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. vercel/next.js was counted at ref canary (commit c20c1d4125b5) on 2026-09-21; remix-run/react-router was counted at ref main (commit 58c47cd00575) on 2026-09-21. See the [counting methodology](https://octocounts.com/docs/methodology) for ignored directories and analysis options.
## About this comparison

vercel/next.js counts the Next.js monorepo — framework packages, documentation site, examples, and test suites. remix-run/react-router counts the React Router repository: the routing library packages, docs, and tests. This is a framework-repository vs library-repository comparison: related layers of the same stack, but not the same kind of software, counted on the dates shown in the methodology line above.

As in the Next.js counts elsewhere on this site, a substantial share of the Next.js total is examples, documentation-site content, and test material — code that teaches and verifies rather than ships as framework runtime.

React Router's repository is scoped to routing: the library packages plus their docs and tests, so its count is closer to a single-purpose library tree, while the per-language tables of both reports show TypeScript as the dominant implementation language for each.

_This is not framework-vs-framework: React Router supplies routing and is typically paired with a separate data and build layer, while Next.js bundles those concerns. Neither number indicates which fits an application better._

Sources: [vercel/next.js repository structure (monorepo with examples and docs)](https://github.com/vercel/next.js) · [remix-run/react-router repository](https://github.com/remix-run/react-router). Statements verified 2026-09-16.

Evidence and next steps:

- [vercel/next.js SLOC report](https://octocounts.com/github/vercel/next.js)
- [remix-run/react-router SLOC report](https://octocounts.com/github/remix-run/react-router)
- [Compare vercel/next.js and remix-run/react-router interactively](https://octocounts.com/compare?left=https%3A%2F%2Fgithub.com%2Fvercel%2Fnext.js&right=https%3A%2F%2Fgithub.com%2Fremix-run%2Freact-router)

Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.

## Compare FAQ

### Which has more lines of code, vercel/next.js or remix-run/react-router?

vercel/next.js has more code: 735,550 code lines versus 104,792 for remix-run/react-router, about 7.0x as much, based on cached OctoCounts reports as of 2026-09-21.

### Does more source lines of code mean more complexity?

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, remix-run/react-router, or any repository.

### How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. vercel/next.js was counted at ref canary (commit c20c1d4125b5) on 2026-09-21; remix-run/react-router was counted at ref main (commit 58c47cd00575) on 2026-09-21. See the counting methodology for ignored directories and analysis options.

### Can I compare a different branch, tag, or commit?

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.

## Related OctoCounts pages

- [Interactive repository comparison](https://octocounts.com/compare)
- [Recently analyzed repositories](https://octocounts.com/recent)
- [Popular SLOC reports](https://octocounts.com/popular)
- [Trending GitHub repositories](https://octocounts.com/trending)
- [Hall of Monoliths](https://octocounts.com/hall-of-monoliths)
- [Original research: how filtering changes SLOC counts](https://octocounts.com/research)
- [GitHub SLOC counter guide](https://octocounts.com/docs/github-sloc-counter)
- [Counting methodology](https://octocounts.com/docs/methodology)
- [SLOC and code metrics glossary](https://octocounts.com/docs/glossary)
- [OctoCounts API docs](https://octocounts.com/docs/api)