TanStack Router Blog

Prefetching in route loaders is great, but comes at a cost. We have to keep loaders in-sync with components...

A navigation looks like one asynchronous operation. Inside TanStack Router, separate owners coordinate matching, loaders, pending UI, redirects, caching, and rendering.

TanStack Router has a built-in cache, so why would we need TanStack Query? There are, of course, reasons ...

TanStack Router, Start, and Query now support the Solid 2.0 beta, so you can try Solid's next major release in real applications today.

TanStack Router now uses a granular signal graph as its reactive core. State is derived from that graph, which narrows change propagation and makes client-side navigation faster in our benchmarks.

A rewrite aimed at fixing edge cases in route matching accidentally delivered a 20,000x performance improvement. Route matching is no longer bottlenecked by the number of routes in your application.

An overview of how TanStack Router automatically shares and infers path params, search params, and context between nested routes in a type-safe way.

Search params are global, serializable, and shareable — but in most apps they're hacked together with string parsing and brittle utils. They deserve to be treated as first-class state.

Yes, it's type-safe, but there's so much more to love about TanStack Router.

The frameworks we choose can make or break our developer experience. Here's why TanStack Start and Router offer a compelling alternative for building modern web applications.

TanStack Router pushes the boundaries on type-safe routing, but large route trees can slow down the editor. Here's how we achieved a major milestone in TypeScript performance.