chore(deps): update dependency react-router to ^6.20.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-router	^6.11.2 -> ^6.20.0

---

Release Notes

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

v6.20.0

Compare Source

Minor Changes

• Export the PathParam type from the public API (#​10719)

Patch Changes

• Fix bug with resolveTo in splat routes (#​11045)
  • This is a follow up to #​10983 to handle the few other code paths using getPathContributingMatches
  • This removes the UNSAFE_getPathContributingMatches export from @remix-run/router since we no longer need this in the react-router/react-router-dom layers
• Updated dependencies:
  • @remix-run/router@1.13.0

v6.19.0

Compare Source

Minor Changes

• Add unstable_flushSync option to useNavigate/useSumbit/fetcher.load/fetcher.submit to opt-out of React.startTransition and into ReactDOM.flushSync for state updates (#​11005)
• Remove the unstable_ prefix from the useBlocker hook as it's been in use for enough time that we are confident in the API. We do not plan to remove the prefix from unstable_usePrompt due to differences in how browsers handle window.confirm that prevent React Router from guaranteeing consistent/correct behavior. (#​10991)

Patch Changes

• Fix useActionData so it returns proper contextual action data and not any action data in the tree (#​11023)

• Fix bug in useResolvedPath that would cause useResolvedPath(".") in a splat route to lose the splat portion of the URL path. (#​10983)

  • ⚠️ This fixes a quite long-standing bug specifically for "." paths inside a splat route which incorrectly dropped the splat portion of the URL. If you are relative routing via "." inside a splat route in your application you should double check that your logic is not relying on this buggy behavior and update accordingly.

• Updated dependencies:

  • @remix-run/router@1.12.0

v6.18.0

Compare Source

Patch Changes

• Fix the future prop on BrowserRouter, HashRouter and MemoryRouter so that it accepts a Partial<FutureConfig> instead of requiring all flags to be included. (#​10962)
• Updated dependencies:
  • @remix-run/router@1.11.0

v6.17.0

Compare Source

Patch Changes

• Fix RouterProvider future prop type to be a Partial<FutureConfig> so that not all flags must be specified (#​10900)
• Updated dependencies:
  • @remix-run/router@1.10.0

v6.16.0

Compare Source

Minor Changes

• In order to move towards stricter TypeScript support in the future, we're aiming to replace current usages of any with unknown on exposed typings for user-provided data. To do this in Remix v2 without introducing breaking changes in React Router v6, we have added generics to a number of shared types. These continue to default to any in React Router and are overridden with unknown in Remix. In React Router v7 we plan to move these to unknown as a breaking change. (#​10843)
  • Location now accepts a generic for the location.state value
  • ActionFunctionArgs/ActionFunction/LoaderFunctionArgs/LoaderFunction now accept a generic for the context parameter (only used in SSR usages via createStaticHandler)
  • The return type of useMatches (now exported as UIMatch) accepts generics for match.data and match.handle - both of which were already set to unknown
• Move the @private class export ErrorResponse to an UNSAFE_ErrorResponseImpl export since it is an implementation detail and there should be no construction of ErrorResponse instances in userland. This frees us up to export a type ErrorResponse which correlates to an instance of the class via InstanceType. Userland code should only ever be using ErrorResponse as a type and should be type-narrowing via isRouteErrorResponse. (#​10811)
• Export ShouldRevalidateFunctionArgs interface (#​10797)
• Removed private/internal APIs only required for the Remix v1 backwards compatibility layer and no longer needed in Remix v2 (_isFetchActionRedirect, _hasFetcherDoneAnything) (#​10715)

Patch Changes

• Updated dependencies:
  • @remix-run/router@1.9.0

v6.15.0

Compare Source

Minor Changes

• Add's a new redirectDocument() function which allows users to specify that a redirect from a loader/action should trigger a document reload (via window.location) instead of attempting to navigate to the redirected location via React Router (#​10705)

Patch Changes

• Ensure useRevalidator is referentially stable across re-renders if revalidations are not actively occurring (#​10707)
• Updated dependencies:
  • @remix-run/router@1.8.0

v6.14.2

Compare Source

Patch Changes

• Updated dependencies:
  • @remix-run/router@1.7.2

v6.14.1

Compare Source

Patch Changes

• Fix loop in unstable_useBlocker when used with an unstable blocker function (#​10652)
• Fix issues with reused blockers on subsequent navigations (#​10656)
• Updated dependencies:
  • @remix-run/router@1.7.1

v6.14.0

Compare Source

Patch Changes

• Strip basename from locations provided to unstable_useBlocker functions to match useLocation (#​10573)
• Fix generatePath when passed a numeric 0 value parameter (#​10612)
• Fix unstable_useBlocker key issues in StrictMode (#​10573)
• Fix tsc --skipLibCheck:false issues on React 17 (#​10622)
• Upgrade typescript to 5.1 (#​10581)
• Updated dependencies:
  • @remix-run/router@1.7.0

v6.13.0

Compare Source

Minor Changes

• Move React.startTransition usage behind a future flag to avoid issues with existing incompatible Suspense usages. We recommend folks adopting this flag to be better compatible with React concurrent mode, but if you run into issues you can continue without the use of startTransition until v7. Issues usually boils down to creating net-new promises during the render cycle, so if you run into issues you should either lift your promise creation out of the render cycle or put it behind a useMemo. (#​10596)

  Existing behavior will no longer include React.startTransition:

  <BrowserRouter>
    <Routes>{/*...*/}</Routes>
  </BrowserRouter>
  
  <RouterProvider router={router} />

  If you wish to enable React.startTransition, pass the future flag to your component:

  <BrowserRouter future={{ v7_startTransition: true }}>
    <Routes>{/*...*/}</Routes>
  </BrowserRouter>
  
  <RouterProvider router={router} future={{ v7_startTransition: true }}/>

Patch Changes

• Work around webpack/terser React.startTransition minification bug in production mode (#​10588)

v6.12.1

Compare Source

Warning
Please use version 6.13.0 or later instead of 6.12.1. This version suffers from a webpack/terser minification issue resulting in invalid minified code in your resulting production bundles which can cause issues in your application. See #​10579 for more details.

Patch Changes

• Adjust feature detection of React.startTransition to fix webpack + react 17 compilation error (#​10569)

v6.12.0

Compare Source

Minor Changes

• Wrap internal router state updates with React.startTransition if it exists (#​10438)

Patch Changes

• Updated dependencies:
  • @remix-run/router@1.6.3

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update 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.