Pick the framework that fits your problem.

The most opinionated full-stack React framework. App Router is the default in 2026; Pages Router is legacy. The right choice for most product builds — for the right reasons, not for hype.

The compiler-first React alternative. Smaller bundles, tighter API surface, and a runtime so light it almost doesn't feel like a framework — until you need an ecosystem feature React already has.

Content-first by default, with islands for the interactive bits. Ships dramatically less JavaScript than React or Svelte for the same page — when the page is mostly content. The wrong tool for app-shaped products.

The web-platform React framework. Now technically part of React Router 7, with the Remix ergonomics merged in. Less marketed than Next.js, more portable, more form-friendly — and increasingly the answer when you want React without the Vercel-shaped opinions.

Vue's Next.js. The most opinionated full-stack framework in the Vue ecosystem, with auto-imports, file-based everything, and a server engine (Nitro) that deploys to nearly every host. The right answer if your team writes Vue.

The fine-grained-reactive metaframework. SolidJS's runtime is so small it almost doesn't feel like a framework, and SolidStart wraps it in a Next.js-shaped full-stack experience. Niche, but the best DX in this set if you can stomach the smaller ecosystem.

The resumability framework. Skips hydration entirely — pages are interactive from first paint without re-executing component code in the browser. The most architecturally novel bet in this set, with the steepest mental model.

The Express of the edge era. A tiny, fast, ultraportable backend framework that runs on every JavaScript runtime that exists. Not a metaframework — there's no client-side rendering layer here. The right answer when you need a backend, not a full-stack framework.