* feat: add reset prop to errorComponent
* fix: types of defaultErrorComponent
* fix: put match into pending state when being invalidated if it was in error state
* docs: reset
* docs: error handling
* docs: integrate error handling into example
* chore: prettier on md files
* chore: fix wrong auto import
* fix: reset error boundaries from react-query in an effect
so that navigating away from a route will also re-trigger the query
* docs: error handling with TanStack Query
* chore: fix eslint
* fix: not all error components have a `preload`
* fix: merge conflict
* feat(router-vite-plugin): trigger router-generator on all events
* feat: safe-guard against additional future events being added in
* feat(router-vite-plugin): use the watchChange hook to handle the route-tree generation
* feat(react-router): return the useNavigate hook
* docs(react-router): update verbiage on the RouteClass doc
* test(react-router): ensure the typed hooks are available across the shared surfaces
* docs: add createLazyFileRoute
* docs: broken link to the FileRouteClass
* docs: remove the word literal
* docs: update the source of its configuration options
* docs: add createLazyRoute
* feat(router-generator): expose config to accept `semicolons` prop to prettier format with semicolons
* docs(router-generator): document the new `semicolons` configuration property
* 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