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
Unable to change the title dynamically per page
_root.tsx
```tsx
import * as React from 'react'...Preventing a specific query from triggering `onError`
Is is possible to use the same component for more than one route ?
Debug response with line number?
Navigate to child pages from parent
Should .ts files be ignored by default with file based routing?
routes-folders I created a .ts-file (beneath the .tsx-files) . After creating the file, the generator plugin generates the typical createFileRoute in that file (and also includes the routes in routeTree.gen.ts). Obviously this does not work, as a .ts file does not support JSX syntax. When removing the generated code from the .ts-file the code is not generated again, but the "route" is not removed from routeTree.gen.ts (which is inconsistent imho).
I didn't found something in the docs nor the source code, so my question is: should .tsfiles be ignored or is it correct that the generator treats them as route files? Personally I'd like to see them ignored, because then I could easily co-locate non-UI files (data loading code, hooks, etc.) with my route files....Update URL hash without scrolling to the element?
Matches after route Param
Redirect in loader causes infinite loop
File based routing /post/new route matching
Style/Best Practices
Authenticated routes with tanstack Query requires window reload
Race condition with beforeLoad and routerContext
tRPC in context or constant?
On refresh, always getting redirected to home page.
/sign-in, redirect to home page.
And the 2nd screenshot is my __root.tsx component where as soon as my auth is done, I call router.invalidate(). This makes sure that beforeLoadruns again....
Lazy loading progress
Need to convert Rust code to run in GPU instead of CPU
Routing with async data
user: User | null:
```
// app.tsx
const {data: user} = useUser();...