* fix: peerDependencies
* docs: requirements
* ci: run type tests against multiple TS versions
* chore: newline
* chore: fix prettier
* fix: wrappers must return a JSX Element
* fix: have Explorer return JSX.Element
* fix: another one
* docs: broken link linking to the SSR guide
* docs: broken link linking to the `RouterOptionsType#transformer-property`
* docs: fix broken link linking to code-splitting
* docs: fix broken link linking to the `RouterOptionsType`
* docs: fix broken link linking to external-data-loading
* docs: include layout as part of the pathless routes section
* docs: add links to the individual sections below
* docs: links for the route nesting stuff
* docs: move the routing concepts section to separate page
accessing `router.state` is an imperative way of reading something from the router - it does not re-render the component; with this fix, we will always re-render the match if the `resetKey` changes, so that the `CatchBoundary` can reset accordingly.
This should fix cases where navigating away from a route did not reset errors correctly
* fix: useNavigate subscriptions
there shouldn't be a need to subscribe useNavigate to useMatch to read the pathname, because we just need it inside the callback, we can read it imperatively
also, there was likely a stale closure problem if `location` changed, as `useMatch` would re-render the component, but `useCallback` wouldn't see the fresh value
* fix: depend on whole router class, because `.state` is an imperative getter
* fix: use resolvedLocation
* fix: useMatchRoute should not subscribe to router state
because we only access it imperatively in the callback, which will always read the latest values from router.state
* fix(react): make sure useMatch errors with a proper message when using `strict`
before this fix, it was dying with a ReferenceError when accessing match!.route
* refactor(react): build `useParams` on top of `useMatch`
so that we get the same error reporting from useMatch
* fix: more generic error message
* chore: ignore the `*.gen.ts` outputs from the `tests` folder in `packges/router-generator`
* chore: add the test script
* test: add tests for 'single-level' routing
* test: add tests for 'flat' routing
* test: amend the 'flat' routing test to include a `route`-level config
* test: add tests for 'nested' routing
* test: match the dir structure between the 'flat' and 'nested' test cases
* test: add tests for complex 'nested-layouts' routing
* chore: disable logging from the `router-generator` package when testing
* chore: space that wasn't supposed to be there
* test: use `routeTree.expected.ts` for storing the expected outputs
* chore: remove comment
* test: run all the generator tests against all its subfolders
* fix: `<TanStackRouterDevtools>` not working when not nested in `<RouterProvider>`
the `<TanStackRouterDevtools` component threw errors when it wasn't rendered inside the `<RouterProvider>` due to some of its calls that relied on this nesting.
* fix: `<TanStackRouterDevtoolsPanel>` not working because of the reliance on `DevtoolsOnCloseContext`
the `<TanStackRouterDevtoolsPanel>` component threw errors on render due to its reliance on the `DevtoolsOnCloseContext` which it wasn't wrapped with
* chore: add large file based routing example to test peformance
- ensure each Link points to a different route to make test realistic
- support absolute and relative pathing for now
* chore: remove posts
* chore: update pnpm lock file
* chore: rename to relative and absolute
* chore: add content to README