Update dependency react-router-dom to v6.28.0

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-router-dom (source)	`6.18.0` -> `6.28.0`

Release Notes

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

### [`v6.28.0`](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.27.0...react-router-dom@6.28.0) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.27.0...react-router-dom@6.28.0) ### [`v6.27.0`](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.26.2...react-router-dom@6.27.0) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.26.2...react-router-dom@6.27.0) ### [`v6.26.2`](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.26.1...react-router-dom@6.26.2) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.26.1...react-router-dom@6.26.2) ### [`v6.26.1`](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.26.0...react-router-dom@6.26.1) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.26.0...react-router-dom@6.26.1) ### [`v6.26.0`](https://redirect.github.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6260) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.25.1...react-router-dom@6.26.0) ##### Minor Changes - Add a new `replace(url, init?)` alternative to `redirect(url, init?)` that performs a `history.replaceState` instead of a `history.pushState` on client-side navigation redirects ([#11811](https://redirect.github.com/remix-run/react-router/pull/11811)) ##### Patch Changes - Fix initial hydration behavior when using `future.v7_partialHydration` along with `unstable_patchRoutesOnMiss` ([#11838](https://redirect.github.com/remix-run/react-router/pull/11838)) - During initial hydration, `router.state.matches` will now include any partial matches so that we can render ancestor `HydrateFallback` components - Updated dependencies: - `@remix-run/router@1.19.0` - `react-router@6.26.0` ### [`v6.25.1`](https://redirect.github.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6251) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.25.0...react-router-dom@6.25.1) ##### Patch Changes - Memoize some `RouterProvider` internals to reduce unnecessary re-renders ([#11803](https://redirect.github.com/remix-run/react-router/pull/11803)) - Updated dependencies: - `react-router@6.25.1` ### [`v6.25.0`](https://redirect.github.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6250) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.24.1...react-router-dom@6.25.0) ##### Minor Changes - Stabilize `future.unstable_skipActionErrorRevalidation` as `future.v7_skipActionErrorRevalidation` ([#11769](https://redirect.github.com/remix-run/react-router/pull/11769)) - When this flag is enabled, actions will not automatically trigger a revalidation if they return/throw a `Response` with a `4xx`/`5xx` status code - You may still opt-into revalidation via `shouldRevalidate` - This also changes `shouldRevalidate`'s `unstable_actionStatus` parameter to `actionStatus` ##### Patch Changes - Updated dependencies: - `react-router@6.25.0` - `@remix-run/router@1.18.0` ### [`v6.24.1`](https://redirect.github.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6241) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.24.0...react-router-dom@6.24.1) ##### Patch Changes - Remove `polyfill.io` reference from warning message because the domain was sold and has since been determined to serve malware ([#11741](https://redirect.github.com/remix-run/react-router/pull/11741)) - See - Export `NavLinkRenderProps` type for easier typing of custom `NavLink` callback ([#11553](https://redirect.github.com/remix-run/react-router/pull/11553)) - Updated dependencies: - `@remix-run/router@1.17.1` - `react-router@6.24.1` ### [`v6.24.0`](https://redirect.github.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6240) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.23.1...react-router-dom@6.24.0) ##### Minor Changes - Add support for Lazy Route Discovery (a.k.a. Fog of War) ([#11626](https://redirect.github.com/remix-run/react-router/pull/11626)) - RFC: - `unstable_patchRoutesOnMiss` docs: ##### Patch Changes - Fix `fetcher.submit` types - remove incorrect `navigate`/`fetcherKey`/`unstable_viewTransition` options because they are only relevant for `useSubmit` ([#11631](https://redirect.github.com/remix-run/react-router/pull/11631)) - Allow falsy `location.state` values passed to `` ([#11495](https://redirect.github.com/remix-run/react-router/pull/11495)) - Updated dependencies: - `react-router@6.24.0` - `@remix-run/router@1.17.0` ### [`v6.23.1`](https://redirect.github.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6231) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.23.0...react-router-dom@6.23.1) ##### Patch Changes - Check for `document` existence when checking `startViewTransition` ([#11544](https://redirect.github.com/remix-run/react-router/pull/11544)) - Change the `react-router-dom/server` import back to `react-router-dom` instead of `index.ts` ([#11514](https://redirect.github.com/remix-run/react-router/pull/11514)) - Updated dependencies: - `@remix-run/router@1.16.1` - `react-router@6.23.1` ### [`v6.23.0`](https://redirect.github.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6230) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.22.3...react-router-dom@6.23.0) ##### Minor Changes - Add a new `unstable_dataStrategy` configuration option ([#11098](https://redirect.github.com/remix-run/react-router/pull/11098)) - This option allows Data Router applications to take control over the approach for executing route loaders and actions - The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix single-fetch, middleware/context APIs, automatic loader caching, and more ##### Patch Changes - Updated dependencies: - `@remix-run/router@1.16.0` - `react-router@6.23.0` ### [`v6.22.3`](https://redirect.github.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6223) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.22.2...react-router-dom@6.22.3) ##### Patch Changes - Updated dependencies: - `@remix-run/router@1.15.3` - `react-router@6.22.3` ### [`v6.22.2`](https://redirect.github.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6222) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.22.1...react-router-dom@6.22.2) ##### Patch Changes - Updated dependencies: - `@remix-run/router@1.15.2` - `react-router@6.22.2` ### [`v6.22.1`](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.22.0...react-router-dom@6.22.1) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.22.0...react-router-dom@6.22.1) ### [`v6.22.0`](https://redirect.github.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6220) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.21.3...react-router-dom@6.22.0) ##### Minor Changes - Include a `window__reactRouterVersion` tag for CWV Report detection ([#11222](https://redirect.github.com/remix-run/react-router/pull/11222)) ##### Patch Changes - Updated dependencies: - `@remix-run/router@1.15.0` - `react-router@6.22.0` ### [`v6.21.3`](https://redirect.github.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6213) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.21.2...react-router-dom@6.21.3) ##### Patch Changes - Fix `NavLink` `isPending` when a `basename` is used ([#11195](https://redirect.github.com/remix-run/react-router/pull/11195)) - Remove leftover `unstable_` prefix from `Blocker`/`BlockerFunction` types ([#11187](https://redirect.github.com/remix-run/react-router/pull/11187)) - Updated dependencies: - `react-router@6.21.3` ### [`v6.21.2`](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.21.1...react-router-dom@6.21.2) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.21.1...react-router-dom@6.21.2) ### [`v6.21.1`](https://redirect.github.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6211) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.21.0...react-router-dom@6.21.1) ##### Patch Changes - Updated dependencies: - `react-router@6.21.1` - `@remix-run/router@1.14.1` ### [`v6.21.0`](https://redirect.github.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6210) [Compare Source](https://redirect.github.com/remix-run/react-router/compare/react-router-dom@6.20.1...react-router-dom@6.21.0) ##### Minor Changes - Add a new `future.v7_relativeSplatPath` flag to implement a breaking bug fix to relative routing when inside a splat route. ([#11087](https://redirect.github.com/remix-run/react-router/pull/11087)) This fix was originally added in [#10983](https://redirect.github.com/remix-run/react-router/issues/10983) and was later reverted in [#11078](https://redirect.github.com/remix-run/react-router/pull/11078) because it was determined that a large number of existing applications were relying on the buggy behavior (see [#11052](https://redirect.github.com/remix-run/react-router/issues/11052)) **The Bug** The buggy behavior is that without this flag, the default behavior when resolving relative paths is to *ignore* any splat (`*`) portion of the current route path. **The Background** This decision was originally made thinking that it would make the concept of nested different sections of your apps in `` easier if relative routing would *replace* the current splat: ```jsx } /> } /> ``` Any paths like `/dashboard`, `/dashboard/team`, `/dashboard/projects` will match the `Dashboard` route. The dashboard component itself can then render nested ``: ```jsx function Dashboard() { return (

Dashboard

} /> } /> } />

); } ``` Now, all links and route paths are relative to the router above them. This makes code splitting and compartmentalizing your app really easy. You could render the `Dashboard` as its own independent app, or embed it into your large app without making any changes to it. **The Problem** The problem is that this concept of ignoring part of a path breaks a lot of other assumptions in React Router - namely that `"."` always means the current location pathname for that route. When we ignore the splat portion, we start getting invalid paths when using `"."`: ```jsx // If we are on URL /dashboard/team, and we want to link to /dashboard/team: function DashboardTeam() { // ❌ This is broken and results in return A broken link to the Current URL; // ✅ This is fixed but super unintuitive since we're already at /dashboard/team! return A broken link to the Current URL; } ``` We've also introduced an issue that we can no longer move our `DashboardTeam` component around our route hierarchy easily - since it behaves differently if we're underneath a non-splat route, such as `/dashboard/:widget`. Now, our `"."` links will, properly point to ourself *inclusive of the dynamic param value* so behavior will break from it's corresponding usage in a `/dashboard/*` route. Even worse, consider a nested splat route configuration: ```jsx } /> ``` Now, a `` and a `` inside the `Dashboard` component go to the same place! That is definitely not correct! Another common issue arose in Data Routers (and Remix) where any `; }, }, ], }); ``` This is just a compounded issue from the above because the default location for a `Form` to submit to is itself (`"."`) - and if we ignore the splat portion, that now resolves to the parent route. **The Solution** If you are leveraging this behavior, it's recommended to enable the future flag, move your splat to it's own route, and leverage `../` for any links to "sibling" pages: ```jsx } /> function Dashboard() { return (

Dashboard

} /> } /> } />

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 this update again.

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

This PR was generated by Mend Renovate. View the repository job log.

maksimMaiboroda / social-network