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 redirect from root layout?

[SOLVED] Does validateSearch not work with createLazyFileRoute?
Object literal may only specify known properties, and 'validateSearch' does not exist in type 'LazyRouteOptions'.ts(2353)
Object literal may only specify known properties, and 'validateSearch' does not exist in type 'LazyRouteOptions'.ts(2353)
Recovery from error in errorComponent
Not valid react child error on simple component
Getting multiple re-renders
useLogRenders hook from this example from an issue I saw on github which could be a similar problem?
In the logs screenshot, I've got no react components being rendered in my Root route....
Getting 'Type instantiation is excessively deep and possibly infinite.' TS error using matchRoute
const matchRoute = useMatchRoute();
const isAccount = matchRoute({ to: '/account' });
const matchRoute = useMatchRoute();
const isAccount = matchRoute({ to: '/account' });

using vinxi with tanstack router, updated example
Search params getting lost when navigating
Link component with search params that is used on different routes. On some of the source routes, the link correctly navigates to the destination route, but on one particular source route, the destination route gets the search params from the source route rather than the search params from the Link.
If I copy the URL from the link and paste it into a new tab, it correctly loads the search params, so I know that the search in the Link is correct....Param masking clears path
path: 'dashboard/$userId.
I also want to use masking to hide some information from the URL.
When I navigate, If I do: ...Why context auth doesn't work if the router is lazy?
Migration from `NotFoundRoute` to `notFoundComponent`
File-based authenticad route is rendered because isAuthenticated is not fetched yet in the context
Squiglies in createLazyFileRoute
Getting a weird error following the react-query-file-based example

Should I use Loader in routes?
opengraph usage with router
ts error when using MatchRoute to identify parametrized child route in the parent route component
/posts route with a list of posts (PostsComponent).
...LayoutIndexImport.update is not a function
routeTree.gen.ts:35 Uncaught TypeError: LayoutIndexImport.update is not a function
at routeTree.gen.ts:35:44
routeTree.gen.ts:35 Uncaught TypeError: LayoutIndexImport.update is not a function
at routeTree.gen.ts:35:44

Disable error component, or enable enable it to retry query.
What is the current way to not trigger whole tree reload (as parent) on sub-tree URL change?
