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
How to test a custom hook that uses tanstack router?!??
Pending matches not working as expected
<MatchRoute /> component with pending flag to show a loading indicator while the router is navigating to a particular route.
I have a loader that fetches data in the route I am navigating to and based on the docs (https://tanstack.com/router/v1/docs/framework/react/guide/navigation#usematchroute-and-matchroute) I expected it to show a loading indicator while the loader was fetching but it doesn't do that.
...If I call via `useMatches` from /products/1234/a,' should each segment be returned as its own match?
useMatches to access all of the matches associated with my current route, should Tanstack Router return all of the routes preceding my current route as well? Say I've navigate to /products/1234/a in the browser. In the array of routes returned by TRR, should I see one for each of these path segments plus layout routes? Right now, I'm not seeing route match for /products in the array.Difference between `router.latestLocation` and `router.parseLocation()`
router.latestLocation might be more performant, but before relying on this I'd like to understand the difference....Way to determine if there is routing history within the app?
router.history.back(), but I don't want it to potentially end up sending the user out of our app. So with react-router@3 we have a helper goBackWithFallback() which takes an optional URL which we navigate to in case going back would send the user out of the apps.
Is there a similar way to determine if there is routing history, and going back one step in history makes us end up in our app?...File structure for nested breadcrumbs [solved]
index.tsx which is exposed under the __root.tsx in the same directory level, one called organizations, and a third. On the root layout I have my shared navbar in the layout, but in the organizations route, I can dive 5 levels deeper. I am having some difficulty figuring out the file structure here for File Based Routing. On the root of the /organizations route I want to include a shared breadcrumb that is persistent on all child routes. I want the file structure to look something like this
```
__root.tsx
index.tsx
organizations...Is there an option to lazy-load a group of routes in one chunk?
Unable to navigate using relative links
``
function DeviceLink({ id, name }: DeviceLinkProps) {
const location = useLocation()
console.log(Location: ${JSON.stringify(location)}`)...Generated tree file isnt being built with Vite
Is there a hook to access router context ?
Lazy file routes don't have the same config as regular file routes?

Blocker does not guard browser back like react-router
react-router is since there it works as one might expect there? ...React Router does not render redirected route after query error
beforeLoad / validateSearch compatibility issue?
beforeLoad (e.g. context) that the type of search parameters provided via inference validateSearch is dropped in consumers utilizing useSearch?
If not, how might one leverage beforeLoad with provided parameters without losing the type inference for search parameters on the same route?
Minimal Repro: https://stackblitz.com/edit/tanstack-router-nrzryj?file=src%2Fmain.tsx...Bug: Never ending "pending" state when notFound is thrown from a splat route
/browse/album/123 URL in StackBlitz
Expected result
A "Not found message"...
Bug: `throw notFound()` in `beforeLoad()` when preloading instantly shows the error
/browse
2. Hover over "Browse 404"...How to hide network request?
Getting the type for the "to" prop
What would cause the `loader` to be called without `context`?
context parameter in the loader function of my route, but randomly, it sometimes throws the error (destructured parameter).context is undefined. Refreshing the page fixes the issue, but I am not sure why the issue is happening in the first place. My beforeLoad method always returns a value (unless the user isn't authenticated, in which case it throws a redirect, but that is not happening here), so from what I can tell, context should never be undefined...
```tsx
export const Route = createFileRoute('/orders/search')({
validateSearch: orderSearchParamsSchema,...