Next.js vs Nuxt

React vs Vue meta.

Overview

Next.js and Nuxt are the two leading meta-frameworks for React and Vue respectively. They solve the same problem (server-side rendering, file-based routing, integrated build tooling, deploy adapters) on different underlying frameworks. The right answer is almost always determined by which underlying framework the team writes already.

• Next.js: React-based. Server Components, App Router, ISR, edge functions. Default when the team writes React.
• Nuxt: Vue-based. Auto-imports, file-based routing, server routes, Nitro deploy. Default when the team writes Vue.
• Operational fit per team. Existing component libraries, design systems, and engineer hiring pool bias toward whichever framework the team already uses.
• Per-app choice. Different apps may pick differently if teams differ. Document the rationale per app.

The approach

Workload-driven choice, per-team operational fit considered, documented rationale per app. The discipline is matching the meta-framework to the team's existing framework expertise rather than choosing the trendier option.

• Workload-driven. Meta-framework per app. Reality drives the answer.
• Next.js for React teams. Default when the team writes React. Hiring pool, library ecosystem, and design-system inheritance all point here.
• Nuxt for Vue teams. Default when the team writes Vue. Same logic on the Vue side.
• Operational fit plus documented rationale. Team framework expertise considered; per-app rationale captured. Future migrations have a paper trail.

Why this compounds

The right meta-framework choice compounds across years. Component libraries and design systems align with the framework; team expertise deepens; cross-app patterns get reused. By year two the framework choice is automatic and the team's velocity reflects the alignment.

• Better operational fit. Framework matches team. Velocity stays high.
• Workload-driven decisions. Replaces tribal preference with documented rationale. Quality of choice improves.
• Better engineering velocity. Right framework means SSR, routing, and build patterns are familiar. Iteration speed increases.
• Year-one investment, year-two habit. First framework choice is the investment; subsequent apps inherit the patterns.