// the find
vercel/next.js
The React Framework
Next.js is the dominant React meta-framework, handling routing, rendering, bundling, and deployment concerns so you don't have to wire them together yourself. It targets teams building production web apps who want SSR, SSG, and RSC without configuring a build pipeline from scratch. At 140k stars it's effectively the default choice for new React projects.
The App Router and React Server Components integration is the most production-ready RSC implementation available — you get streaming, nested layouts, and server-side data fetching with actual caching semantics. The Turbopack bundler (Rust-based, replacing Webpack) now handles dev mode and is meaningfully faster on large codebases — cold starts and HMR are night-and-day compared to a year ago. Image and font optimization are genuinely good defaults that save real bytes without custom config. The repo itself is well-run: typed test infrastructure, integration test manifests, automated stats tracking on bundle size and performance regressions.
The App Router caching model is still notoriously confusing — fetch caching, router cache, full-route cache, and revalidation all interact in ways that bite people in production and have required multiple rounds of breaking changes to fix. Vercel-hosted features (ISR edge cases, Partial Prerendering, some middleware behaviors) work better on Vercel's own infra than on self-hosted deployments, which is an obvious conflict of interest that occasionally shows up as rough edges. The framework surface area has grown large enough that staying current requires constant attention — the Pages Router to App Router migration is still incomplete for many teams and the two routers have meaningfully different mental models. TypeScript config, turbopack feature flags, and experimental options accumulate fast and the interaction matrix is undertested.