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 can I execute several navigations sequentially?
onUserSelect and an onUserClick callback. My eventhandler of the onUserSelect, looks like this:
```js...useMutation Error and Type Safe
Is useNavigate available in components set by InnerWrap?
useNavigate hook in an InnerWrap component we get:
Uncaught TypeError: Cannot read properties of undefined (reading 'routeId')
Uncaught TypeError: Cannot read properties of undefined (reading 'routeId')
useRouterState appears to work fine....Get loader function context type for a route?
export const loader = (ctx: <context type for "/foo">) => ......How to track page views?
posthog-js (similar to Google Analytics) to track page views, since tanstack router navigates on the client side, I need to manually trigger the tracking method.
```
const rootRoute = new RootRoute({
beforeLoad: () => {...Should HMR Work?
loader, making any change to the code triggers a full refetch of the data. Is this intentional or is it something about my setup.
Things I've tried:
- adding staleTime to the route to try to keep it from refreshing...Register.router type error

Pathless directories after dynamic directory not being excluded in url?
/123/detail-layout/route2/123 but the route ID is /_auth/$teamId/_detail-layout, detail-layout is included in the URL
- original layout route which is nested in _auth but not $teamId works as expected, with runtime path /layout-a...useMatchRoute
matchRoute({ to: '/posts', fuzzy: true })
matchRoute({ to: '/posts', fuzzy: true })
Protect the whole app
Integrating reusable tanstack table

Return `fullPath` property from `new RouteApi({ id : "..." })`
fullPath property use required to for example use the navigate function with both from and search, but new RouteApi({ id : "..." }) only returns the route id, which generates type errors when trying to do something like this:
```ts
const navigate = useNavigate()...Search params example raises type errors
Basic router question on routing outside of context
router.navigate({ to: '/dashboard', replace: true }); by importing router outside of the useNavigate context. This is because I want my auth listener to handling routing to/from login state and this lives in main.tsx at the parent level of RouterProvider.
My question is, is it safe to just import router and call router.navigate({ to: '/dashboard', replace: true }); right away or should I check for any kind of initialization or existence before calling navigate right away?
Also if there is a better way to handle this I would appreciate any help, this is how my code is set up currently
main.tsx has
```const renderApp = () => {...Multiple routers
Invalidate loader data
queryClient.invalidateQueries and it doesn't seem to work
Here is my loader
```tsx
export const Route = new FileRoute(...Not found routes with CLI?
Handling CSS and SSR hydration
__root.tsx file that declares the well known
```html
<html>
<head></head>...Search params on the home route
basic-ssr-streaming-file-based example and I now have a loader and loaderDeps on that route to load pages of data for the home route. The initial render works fine, I get whatever page was sent in and retrieve the data in the loader. But when I use a Link to navigate to subsequent pages the URL updates but the content of the page doesn't reload. Does that need to be in a nested route or something? I was hoping it would just update the page with the new content...Implicit any Typescript error on index route under layout
'Route' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.
'Route' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.