Frontend

TanStack Start:
• full-stack meta-framework for React
• TanStack Router with type-safe, stateful URLs (including search params) and atomic state management
• isomorphic loader functions (both server- and client-side), like Remix and SvelteKit
• default caching/invalidation handled by a mini-version of TanStack Query
• based on Vinxi, which uses Nitro for server features and Vite for bundling (similar to SolidStart)
• eventual support for React Server Functions

TanStack Start:
• full-stack meta-framework for React
• TanStack Router with type-safe, stateful URLs (including search params) and atomic state management
• isomorphic loader functions (both server- and client-side), like Remix and SvelteKit
• default caching/invalidation handled by a mini-version of TanStack Query
• based on Vinxi, which uses Nitro for server features and Vite for bundling (similar to SolidStart)
• eventual support for React Server Functions

https://youtu.be/AuHqwQsf64o

/frontend dev・founder/decentralized data wrangler /blockhead・ritual.net・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx・x.com/darryl__yeo

why would i start again when i’ve been building on next for 5 years?

software artist | building /outpaint | ex: @coinbase ex: bisontrails | seeker of the flow state

Depends on your project and whether the switching costs are worth the benefits for you!

even for new projects, what’s the 1 liner? if it’s just fun then that’s cool but i would rather learn rust at that point. or build my fitness app.

or learn to sleep 8 hours.

priorities.

got it. thanks! saved me from reading their docs.

I’d say TanStack Start’s main draw compared to other full-stack frameworks is granular control over route URLs and caching behavior.

If you’re already comfortable with Next.js and what it has to offer in those two departments, by all means stick with what you know.