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

for the same reason you switched to next 5 years ago :)

it highly depends on your use case. next is clearly server-first and if you have a huge bundle that serves different variations of your app but your user is expected to use only a small part of it — then, yes, nextjs is your solution to compute everything on the server and ship down the html

but... if your app is mostly client (like most web3 dapps are) next might stay in your way and a solution like tanstack would be more beneficial.

next was in the right place at the right time, when CRA got deprecated everyone looked for an alternative. now it's time to explore options that cater our exact use cases :)