React Router 7 (formerly Remix)

Remix merged into React Router and now ships as React Router 7. The "framework mode" of React Router is the spiritual successor to Remix; the "library mode" is the same React Router you know from SPA days.

Components

• React Router 7 in framework mode (file-based routes, loaders, actions)
• Vite as the bundler
• TypeScript with generated route types
• Any DB / ORM / auth — the framework is unopinionated
• Deploys to Node, Cloudflare Workers, Deno Deploy, Bun, Vercel, Netlify, Fly.

What it's good at

• Web platform alignment — <Form> posts to actions, loaders fetch on navigation, error boundaries are first class.
• Nested layouts and parallel data loading — the routing model encourages thinking in layout slots.
• Less magic than Next.js App Router — you'll know what's serialized, when, and why.
• Edge-friendly — straightforward to deploy to Cloudflare Workers.

What you give up

• Smaller third-party-component ecosystem of "drop-in" pieces (e.g. Vercel Analytics, Vercel OG image, etc., all assume Next.js).
• No equivalent of Server Components (yet) — RSC support is in active development for React Router framework mode.
• More wiring you do yourself (caching, ISR, image optimization).

When to pick

• You like the loader/action mental model and find the App Router opaque.
• You want to deploy to Cloudflare or another edge target without Next.js shims.
• Your app benefits from nested layouts and progressive enhancement (forms that work without JS).

When to skip

• You want Vercel-tier defaults and don't want to assemble them yourself.
• You're heavily invested in RSC patterns from recent Next.js.