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
Does navigation cause wasteful re-renders?
Throw notFound() gets me a blank page
Is it possible to trigger beforeLoad of a folder index route and respective sub routes?

Search param changes invalidates loaders for all layouts
beforeLoad
for auth in the top layout, could that be causing this?routeTree gen in JS
Save history for search params
React.useId causes hydration errors
Warning: Prop `id` did not match. Server: "react-aria-:Rb3aH1:" Client: "react-aria-:R2oqH1:"
Warning: Prop `id` did not match. Server: "react-aria-:Rb3aH1:" Client: "react-aria-:R2oqH1:"
Intended behaviour for navigation
<host>/auth/logout
and I create a link to it I get typescript autocompletion that first defaults to
```ts
<Link to="auth/logout">
Logout
</Link>...Redirect from validateSearch to the same route with fixed query params using replace
react-router
, but we're investigating switching to this library. We're using query params quite heavily in our app and we'd like to be able to validate and fix them inside the router and not components, to avoid the initial render of a component with the invalid state.
If the query params are not valid, is there a way to redirect from the router to the same route, but with updated query params, by replacing the invalid entry in the browser's history stack?...breaking change?

fetch next page
fetchNextPage
is being executed?
i wanted to use the document data (retrieved from the initial fetch) as my cursor instead of incementing or decrementing one by one....Auth / beforeLoad / router.invalidate / redirect problem with router context update
Attempting to navigate to `./` causes type error in new version
./
shows a type error asking for params
:
```
const navigate = useNavigate();
...
Router.status is always "pending" when you wrap the `RouterProvider` in `StrictMode`.
RouterProvider
in React.StrictMode
, the status of the Router will always be "pending". This also happens with the "basic-file-based" example on GitHub (https://github.com/tanstack/router/tree/main/examples/react/basic-file-based). Is this correct behavior?
Due to this issue, you can never get the correct resolvedLocation, because this will always return the first location you visited....How to get type of Component which create by using createLink() function? Thanks
Declarative search param masking is lagging
example.com/list
and not example.com/list?page=1&search=&sortBy=date&sortOrder=asc&status=active&...
.
https://codesandbox.io/p/devbox/tsr-search-masking-question-vcds2n
A simplified example is this route mask:...What is the preferred/recommended way to implement protected routes?
loader vs beforeLoad
Title Not Setting on Document in Meta Route Prop
