router icon indicating copy to clipboard operation
router copied to clipboard

🤖 Fully typesafe Router for React (and friends) w/ built-in caching, 1st class search-param APIs, client-side cache integration and isomorphic rendering.

Results 526 router issues
Sort by recently updated
recently updated
newest added

Ref: https://github.com/TanStack/router/issues/1756#issuecomment-2198536173 !!! Work in progress, not working yet !!!

### Describe the bug When calling a server function inside another server function, the parameters get altered unexpectedly, causing the outer function to receive modified parameters. This issue prevents the...

bug
start

### Describe the bug using the latest version, the loader with loaderDeps doesn't run initially. the page needs to be reloaded for it to run. Reproduction on version ^1.20.4 (✅...

This is an early quick-start guide for TanStack Start. I haven't added it to the routes configuration guide yet, as I'm not sure how public we want this guide to...

### Describe the bug When a `validateSearch` function gets executed and overrides a search param, the lazy loaded components for that route won't render. With the following code: /test/route.tsx ```code...

> This PR builds on top of #1857, we might want to merge that one first. This PR documents usage of `createServerFn` from TanStack Start. Like the other PR, this...

### Describe the bug For some unknown reason context is undefined in loader, but it was present in beforeLoad ### Your Example Website or App https://github.com/Arilas/tanter-bug ### Steps to Reproduce...

### Describe the bug When you open one of the kitchen sink examples, the route breaks when you navigate to the invoices. Given the fact that I experience issues with...

### Describe the bug When using navigation (e.g. `navigate` / `redirect`) with a `from` and relative `to`, it seems TypeScript always complains about the `search` param being required, even if...

### Describe the bug If you `throw notFound()` for a `$param` param route with a delay (e.g. when awaiting a request), the parent routes stay forever stuck in "pending" state....