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
Astro Example
Is there any obvious problem that you can see?
When preloading and then navigating to a link, should the loader function always run twice?
preload=true when someone hovers over the link, and then preload=false when you actually click and navigate to that link.
However, I'm seeing that sometimes the loader doesn't run the second time, particularly if you click on a link while the lazy component is loading. Is this expected?...FullSearchSchema - why do we need it at all?
how to navigate to a route that has search params with default values?
File Based Router - Layouts
getParentRoute is not a prop of FileRoute so I'm not sure how to do it...Mantine ModalManager + Tanstack Router
Wrap).
Error - Uncaught TypeError: Cannot read properties of null (reading '__store')
Homework - ...Navigating in unit tests
Issue with authenticated routes, redirect and context
router.history.push I get an error on the function that use checks the context if the user is logged in, I need to refresh the page than it works. there error is "Invalid state" from the auth0 library and Warning: Error in route match: root
Here is what I have now:...Shared paths for different users but requiring different search params
Guidance on passing hooks to router context?

Redirect for home page
/ path to redirect to another route for logged in users, the approach below seems to work but I'm not sure it's the right way to do it?
```
const indexRoute = new Route({
getParentRoute: () => rootRoute,...Removing `<Link />` styling
<Link /> styling? The styling in our app is handled by Mantine's NavLink component. Wondering if there's a default way of removing styling or passing something like unstyled to the Link component. Thanks!Issues with authenticated routes
Best way to pass route location to reusable components?

Getting the active path: Best Practices
Subscribe to Route Changes
router.subscribe the best way to re-render a component when a route changes? I feel like I'm missing something, is there a simpler approach?
```
const router = useRouter();
const [matchedRouteIds, setMatchedRouteIds] = useState(
router.state.matches.map((m) => m.id)...Why ensureQueryData instead of prefetchQuery?
Passing context to a component in separate file? / Accessing useRouteContext