react-query-questions
solid-query-questions
table-questions
virtual-questions
router-questions
react-charts-questions
ranger-questions
vue-query-questions
svelte-query-questions
bling-questions
form-questions
angular-query-questions
start-questions
db-questions
start-showcase
router-showcase
š£-announcements
Is it possible to have a route with __ in the path?
Using virtual routes to load routes from an external package
Understanding beforeLoad
Route.useRouteContext()
is typed with { auth: User }
and not { auth: User | null }
.
Then I asked about it and Manuel Schiller help me to find out the problem. But then I wanted to understand how it works better so I cloned the router repository and read how the beforeLoad
works here: https://github.com/TanStack/router/blob/d9a97e2693a726342ed8e9bda6af190902f34077/packages/react-router/src/router.ts#L2168. And I saw that before launching beforeLoad the context seems to add prev.__beforeLoadContext
so I thought it's the previous beforeLoadContext value of the route match...are intercepting routes possible like in nextjs?
Search mask lagging behind by an update
Question regarding nested layouts
data loader only on first render
React router to Tanstack router migration
implementing the breadcrumbs example in docs to a typescript project
Route implicitely has type 'any' because of loader
CreateLink makes all routes "active"
NavLink
with the type safety of Tanstack's Link
component.
I followed this link
https://tanstack.com/router/latest/docs/framework/react/guide/custom-link#createlink-with-third-party-libraries...handleSerialError fails when setting err.routerCode with TypeError(s)
Get all Search Objects

route.tsx pendingComponent is rendering when index.tsx loader runs
react context provider is not updating router context

I don't know the difference between useDataLoader and useSuspenseQuery.
layouts beforeload
HTTP Session Cookie
Router Loaders parallelism in a CRM app project
/entity/$entityId/entityBs
or /entity/$entityId/entityBs/$entityBId
. My problem is what is $entityId
does not exists server-side, all the loaders of the child routes still gets executed for no reason since we know the parent does not exist.
Any advices? Should I only be using loaders for my top-level entity page and not for nested routes?
...