chore(deps): update react-router monorepo to ~6.11.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-router	~6.10.0 -> ~6.11.0
react-router-dom	~6.10.0 -> ~6.11.0

---

Release Notes

remix-run/react-router (react-router)

v6.11.0

Compare Source

Patch Changes

• Log loader/action errors to the console in dev for easier stack trace evaluation (#​10286)
• Fix bug preventing rendering of descendant <Routes> when RouterProvider errors existed (#​10374)
• Fix inadvertent re-renders when using Component instead of element on a route definition (#​10287)
• Fix detection of useNavigate in the render cycle by setting the activeRef in a layout effect, allowing the navigate function to be passed to child components and called in a useEffect there. (#​10394)
• Switched from useSyncExternalStore to useState for internal @remix-run/router router state syncing in <RouterProvider>. We found some subtle bugs where router state updates got propagated before other normal useState updates, which could lead to footguns in useEffect calls. (#​10377, #​10409)
• Allow useRevalidator() to resolve a loader-driven error boundary scenario (#​10369)
• Avoid unnecessary unsubscribe/resubscribes on router state changes (#​10409)
• When using a RouterProvider, useNavigate/useSubmit/fetcher.submit are now stable across location changes, since we can handle relative routing via the @remix-run/router instance and get rid of our dependence on useLocation(). When using BrowserRouter, these hooks remain unstable across location changes because they still rely on useLocation(). (#​10336)
• Updated dependencies:
  • @remix-run/[email protected]

remix-run/react-router (react-router-dom)

v6.11.0

Compare Source

Minor Changes

• Enable basename support in useFetcher (#​10336)
  • If you were previously working around this issue by manually prepending the basename then you will need to remove the manually prepended basename from your fetcher calls (fetcher.load('/basename/route') -> fetcher.load('/route'))

Patch Changes

• Fix inadvertent re-renders when using Component instead of element on a route definition (#​10287)
• Fail gracefully on <Link to="//"> and other invalid URL values (#​10367)
• Switched from useSyncExternalStore to useState for internal @remix-run/router router state syncing in <RouterProvider>. We found some subtle bugs where router state updates got propagated before other normal useState updates, which could lead to footguns in useEffect calls. (#​10377, #​10409)
• Add static prop to StaticRouterProvider's internal Router component (#​10401)
• When using a RouterProvider, useNavigate/useSubmit/fetcher.submit are now stable across location changes, since we can handle relative routing via the @remix-run/router instance and get rid of our dependence on useLocation(). When using BrowserRouter, these hooks remain unstable across location changes because they still rely on useLocation(). (#​10336)
• Updated dependencies:
  • [email protected]
  • @remix-run/[email protected]

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.