build(deps): update react-router monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@remix-run/router	^1.5.0 -> ^1.6.0
react-router-dom	^6.10.0 -> ^6.11.0

---

Release Notes

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

v1.6.0

Compare Source

Minor Changes

• Enable relative routing in the @remix-run/router when providing a source route ID from which the path is relative to: (#​10336)

  • Example: router.navigate("../path", { fromRouteId: "some-route" }).
  • This also applies to router.fetch which already receives a source route ID

• Introduce a new @remix-run/router future.v7_prependBasename flag to enable basename prefixing to all paths coming into router.navigate and router.fetch.

  • Previously the basename was prepended in the React Router layer, but now that relative routing is being handled by the router we need prepend the basename after resolving any relative paths
  • This also enables basename support in useFetcher as well

Patch Changes

• Enhance LoaderFunction/ActionFunction return type to prevent undefined from being a valid return value (#​10267)
• Ensure proper 404 error on fetcher.load call to a route without a loader (#​10345)
• Deprecate the createRouter detectErrorBoundary option in favor of the new mapRouteProperties option for converting a framework-agnostic route to a framework-aware route. This allows us to set more than just the hasErrorBoundary property during route pre-processing, and is now used for mapping Component -> element and ErrorBoundary -> errorElement in react-router. (#​10287)
• Fixed a bug where fetchers were incorrectly attempting to revalidate on search params changes or routing to the same URL (using the same logic for route loader revalidations). However, since fetchers have a static href, they should only revalidate on action submissions or router.revalidate calls. (#​10344)
• Decouple AbortController usage between revalidating fetchers and the thing that triggered them such that the unmount/deletion of a revalidating fetcher doesn't impact the ongoing triggering navigation/revalidation (#​10271)

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:
  • react-router@6.11.0
  • @remix-run/router@1.6.0

---

Configuration

📅 Schedule: Branch creation - "on the 1st day of the month" in timezone Asia/Shanghai, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (86557bc) 82.47% compared to head (d755e02) 82.47%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #561   +/-   ##
=======================================
  Coverage   82.47%   82.47%           
=======================================
  Files          98       98           
  Lines        5952     5952           
  Branches      422      422           
=======================================
  Hits         4909     4909           
  Misses       1037     1037           
  Partials        6        6           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[github-actions]

Preview Deployment

Build	URL	time
Sites	netlify preview	2023-04-01 02:16:11Z
Storybook	netlify preview	2023-04-01 02:17:28Z

[mergify]

@renovate[bot] this pull request is now in conflict 😩

[mergify]

@renovate[bot] this pull request is now in conflict 😩