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
Optional parameter route
workspace and workspace/${id} using a single component without registering two separate routes.Nested file route not create nested routes

Active props className will not work properly when preSearch or postSearch
Router Context not updating
Is it possible to add a route to the routeTree?
routeTree , I have tried casting routeTree to a Route and calling routeTree.addChildren but it results in losing in all my routes.Pending component for layout routes
Algolia search is broken?
Cannot get context value on child route

access the new route object from a router event handler
File-base router for dashboard project
on route change show full screen loader is it possible?
hiii want to know how can i get the the state which we pass in the navigate({to: url , state :{x})
Matching multiple siblings at the same time
State property not wanting to accept new parameters and needed a type casting when using!
validateSearch using async data
loaderDeps does not provide `{ context }`
loaderDeps from context not search (see docs: https://tanstack.com/router/latest/docs/framework/react/api/router/RouteOptionsType#loaderdeps) but it seems only search is defined? Is that a bug or on purpose?
If it is on purpose, why is it only possible to define search params as loaderDeps? Since I use the context in the loader to pass data from the context as fetch arguments, I would like the loader to be triggered again as soon as the context data I'm using changes.
Reference:...Upcoming Preloading Strategies: Progress and Release Date?

Infer valid "to" types for a root router instance
to /from in it's props. I want to get the typing that I would normally get from the native <Link> and useNavigate functions....Default location if no back history?
router.history.back() but if the user for whatever reason refreshes the page all of the history they can go back to is gone. Thus causing my back button to just refresh the page.
How can I provide a default location to navigate to if there is no back history to go to? Or how can I detect if there's history to go back to, so can instead run a navigate() to a fallback location?...Why to use `from` in navigations
from is used when navigating.
Take this example from docs https://tanstack.com/router/latest/docs/framework/react/guide/navigation#usenavigate:
...