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
Use explicit params on loader function
"/_layoutMain" which is basically my layout.
Now I also have a "/channels/$guildId" route.
But In the loader of "/_layoutMain" I need to get the "$guildId" of "/channels"
But the loader param object is now type of Record<never, string> So I can't convince it that there is indeed a param here....Why can modules.data be undefined here?
Disable loaderData cache
Redirect behaviour on child pages
/dashboard
/dashboard
/dashboard/user
/dashboard/user
/dashboard/admin
/dashboard/admin
is using route.fullPath still possible for index routes with trailingSlash never?
Getting access to the isLoading state when using queryClient.ensureQueryData() within TSR
Context is undefined in 'loader'

Refresh Route on Auth Change
Clerk auth
Purpose of `from` for JavaScript users
Type "../../" is not assignable to type "../../../"
../../../ I get: Type "../../../" is not assignable to type "../../../../" and so one....How would I achieve this route pattern?
/ducks - list of all ducks
/ducks/detail/$duckId - modal showing duck details over top of list (<Outlet /> inside /ducks?)
/ducks/new - form to create new duck, but should be full page, not inside /ducks Outlet
Layouts? what would the file/folder structure look like?...Router example with react query is slow to swap components
chrome extension: file-based routing
chrome-extension://[hash_id]/index.html. How can I define this type of route with file-based routing instead of defining a $index and then redirect to the /something/*?navigate does not trigger new page
```typescript...
dist/Index.html shows route not found after vite build in dist folder

Best practices for getRouteApi() with optional path param?
getRouteApi() when rendering the same element for the index route as well as optional the same route with an optional param?
Since TSR doesn't support optional params out of the box we need to define two routes:
* /search
* /search/playlists...Should `prefetchQuery` be await'ed inside the route's `loader`?
queryClient.prefetchQuery inside of a route's loader method. Based on my understanding of both methods, it seems like I would not want to await the prefetchQuery calls since it would block the route from rendering until the query/queries are finished fetching rather than handling the loading state inside the component.
For example:
```tsx
export const Route = createFileRoute('/orders/search')({...Auth Guarded Route doesn`t load lazy component
