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
File-based routing bug or misconfig?
Cannot read properties of undefined( reading 'routeId')

Throwing a not found route with Navigate?

CLIKENT SIDE ERROR USING TANSTACK

tsr generate not working
The "paths[0]" argument must be of type string. Received undefined
I have a trs.config.json file, i have routeTree.gen.ts file, i have a routes folder where I have three files -> __root.tsx, _layout.tsx, index.tsx...Breadcrumbs
/segment
- /segment/$id...On subroute path/url change, whole tree reloads?
/product/<product_category/<product_Id> and just the product id changes, all of the load property on the new Route() setup is retriggered.
That means when the product_id changes, /product/<product_category> retriggers its actions in the load function. The same for /product, the load function is triggered as well here, even tho the <product_id> has changed.
...Global named route object
Detach component from route declaration, typescript vs vite
component function in the route definition gave me the useRouteContext, and different hooks as props, and now I don't have that....Question on catch-all routing
useSearch does not work when you pass a string to form, instead of `route.id`
index routes
Structure for react-refresh
Route objects from one file per route and inline my components in the Route options to get the typescript props automatically, but that causes react-refresh to fail. Exporting both the Route and the component from the same file as separate consts causes eslint react-refresh warnings.Hi, I'm trying to use infiniteQuery in version 5, but the typing is not returning the item pages

router-cli Usage
router-cli in my project, but when I run the generate command, I got this error:
```
/usr/local/bin/tsr: line 1: /Applications: is a directory
/usr/local/bin/tsr: line 2: README.md: command not found
/usr/local/bin/tsr: line 3: README.md: command not found...Is it possible to navigate to update searchParams without remounting the component?
Outlet does not render when using @testing-library/react.
@tanstack/react-location with an existing project that was previously using react-router-dom. Version in package.json is ^3.4.4 - this is because I am implementing a Module Federation solution that already exists in another project, and wanted to keep the versions in sync for the time being.
All is working well, and I hasn't had any issues with dev. However, my integration tests appear to be failing due to the <Outlet /> component not rendering the element associated with the route I'm feeding it....router.navigate has been removed
router.navigate come back, or is this option to navigate no longer available?
will something like this be possible?
...Update search params without rerender
Is it advisable to make heavy use of SearchParams?
It is tempting to handle a complete filter state in the address bar. Then the history works and it's a great user experience, but is it really advisable to handle a large filter state with the help of the SearchParams. I mean a pagination-filter with about 10 filter values, which also consist of complex types. Isn't it possible that you reach limits? Thanks...