Reasons to Still Use Next.js from a TanStack Start Enjoyer

Why You Might Still Pick Next.js Over TanStack Start

From a TanStack Start fanboy

TanStack Start is exciting. File-based routing, type-safe search params, and a stack that feels modern and, most importantly, lets you keep your SPA goodies and cool libraries like TanStack Query to maximize UX for your users and DX for yourself. We all know how heavy-handed mutations can be in Next.js, but with TanStack it all feels like a breeze. Lately, with server components quietly encroaching on Next.js territory, and a rising number of job postings asking for TanStack skills, the ecosystem is clearly growing.

That said, Next.js still wins in a few places that matter in production. This isn't a dunk on TanStack. It's a short list of reasons you might still choose Next.js, especially for mostly-static content sites.

1. Static Server State, Prebuild, and ISR

To be clear: this is not about TanStack Query client caching. This is about static server state: how Server Components and page output get stored, served, and regenerated on the server (Next's Full Route Cache / Data Cache style setup). Off Vercel that usually means wiring a KV (or similar) so the framework can actually persist that page-level server state. On Vercel, a lot of that plumbing is already there.

Next.js makes this easy. You declare revalidation once and the framework owns the rest:

typescript

1// Next.js -- page-level ISR / static server state
2export const revalidate = 3600 // regenerate at most once per hour
3
4export default async function BlogPost({
5  params,
6}: {
7  params: Promise<{ slug: string }>
8}) {
9  const { slug } = await params
10  const post = await getPost(slug)
11  return <Article post={post} />
12}

TanStack Start does have prebuild capabilities, but you still end up manually setting cache headers (or whatever your platform expects) to get proper edge/CDN behavior. Cloudflare made this friendlier with Workers Cache and solid stale-while-revalidate support (so the pieces exist), but Next's declarative revalidate, revalidatePath, and revalidateTag story is cleaner when SEO and freshness matter at scale. Less platform glue, more "set a number and ship."

2. Suspense-Aware Routing (and the Query-Param Flicker)

Next's data fetching and router integrate more cleanly with Suspense. TanStack Router leans on an external store for a lot of its state, and that store doesn't register with Suspense the way you'd hope.

A common pain point: a list driven by search params (filters, page, sort). Change a param, TanStack tracks it, your useSuspenseQuery re-suspends, and the Suspense boundary flickers.

Reasons to Still Use Next.js from a TanStack Start Enjoyer

Tanstack DB in action

🎨 TanStack Start SSR-Friendly Theme Provider

How to get the Oauth providre access tokens from next auth/authjs

Reasons to Still Use Next.js from a TanStack Start Enjoyer

Tanstack DB in action

🎨 TanStack Start SSR-Friendly Theme Provider

How to get the Oauth providre access tokens from next auth/authjs

Why You Might Still Pick Next.js Over TanStack Start

1. Static Server State, Prebuild, and ISR

2. Suspense-Aware Routing (and the Query-Param Flicker)

3. Image and Font Optimization

4. React Canary Features (View Transitions) Built In

5. Ecosystem Fit

Closing: When I'd Still Bite the Complexity and Pick TanStack Start

More posts

Tanstack DB in action

🎨 TanStack Start SSR-Friendly Theme Provider

How to get the Oauth providre access tokens from next auth/authjs

More posts

Tanstack DB in action

🎨 TanStack Start SSR-Friendly Theme Provider

How to get the Oauth providre access tokens from next auth/authjs

Why You Might Still Pick Next.js Over TanStack Start

1. Static Server State, Prebuild, and ISR

2. Suspense-Aware Routing (and the Query-Param Flicker)

3. Image and Font Optimization

4. React Canary Features (View Transitions) Built In

5. Ecosystem Fit

Closing: When I'd Still Bite the Complexity and Pick TanStack Start