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
Tanstack router loader vs. tanstack query

Tab layout transitions
Is it possible to keepPreviousData when using a deferred loader?
TanStack router crashses when seeing a .glsl file
Private field '#version' must be declared in an enclosing class
Private field '#version' must be declared in an enclosing class
File Route Component Best Practices
Is this use of FileRouteTypes['to'] valid?
Link
component and the to
prop is dynamic. I get the value of the to
prop by calling my getConfigureModeLink
function.
To ensure the function can only return a valid registered route I have typed it's return type as FileRouteTypes['to']
which is the interface exported from routeTree.gen.ts
....testing broken after update to 1.120.3
Tanstack router: Not a good experience so far.

Is beforeLoad supposed to run in this situation?
__root.tsx
file, I check a session against my auth server in beforeLoad
so I can update the router context.
In a sub route, if I go from /a
to /b
, is there a way to preserve the context without having to re-run the root beforeLoad
hook? (or any parent beforeLoad
hook really)
For context, my issue is that currently it's very slow because it makes a ton of requests for every page change...change url in address bar without navigating
window.history.replaceState(null, "", newUrl)
window.history.replaceState(null, "", newUrl)
Tanstack router for protected route

SuperTokens integration with Router
Setting global search params
bad setState
useSuspenseQuery
I get this error
Cannot update a component while rendering a difference component...Caching a data loader's output with staleTime not working
staleTime
)
3) When the staleTime
is hit, serve cache data one more time, rebuild cache under the hood for the next request...How to achieve type safety in this scenario?
Directory Structure Best Practice
components
and services
inside the routes directory.
2. Separated: where you put each features extra directories inside a shared component
or feature
directory....
Layout only files

useNavigate to change search params without remounting the route componen
useNavigate()
to change just the search params, but it unnecessarily flashes due to unmounting and mounting the route component again. Is there a mode of operation where it "just" updates the URl with history push but doesn't re-mount the Route component?
My code:
```typescript...i18n Routing - Question