Update dependency react-router-dom to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
react-router-dom (source)	^6.14.2 → ^7.18.3

---

Release Notes

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

v7.18.3

Compare Source

v7.18.2

Compare Source

v7.18.1

Compare Source

v7.18.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.18.0

v7.17.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.17.0

v7.16.0

Compare Source

Patch Changes

• Remove stale/invalid unpkg field from package.json. This was removed from other packages with the release of v7 but missed in the react-router-dom re-export package (#​15075)
• Updated dependencies:
  • react-router@7.16.0

v7.15.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.15.1

v7.15.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.15.0

v7.14.2

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.14.2

v7.14.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.14.1

v7.14.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.14.0

v7.13.2

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.13.2

v7.13.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.13.1

v7.13.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.13.0

v7.12.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.12.0

v7.11.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.11.0

v7.10.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.10.1

v7.10.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.10.0

v7.9.6

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.9.6

v7.9.5

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.9.5

v7.9.4

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.9.4

v7.9.3

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.9.3

v7.9.2

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.9.2

v7.9.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.9.1

v7.9.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.9.0

v7.8.2

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.8.2

v7.8.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.8.1

v7.8.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.8.0

v7.7.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.7.1

v7.7.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.7.0

v7.6.3

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.6.3

v7.6.2

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.6.2

v7.6.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.6.1

v7.6.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.6.0

v7.5.3

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.5.3

v7.5.2

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.5.2

v7.5.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.5.1

v7.5.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.5.0

v7.4.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.4.1

v7.4.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.4.0

v7.3.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.3.0

v7.2.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.2.0

v7.1.5

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.1.5

v7.1.4

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.1.4

v7.1.3

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.1.3

v7.1.2

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.1.2

v7.1.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.1.1

v7.1.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.1.0

v7.0.2

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.0.2

v7.0.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.0.1

v7.0.0

Compare Source

Major Changes

• Remove the original defer implementation in favor of using raw promises via single fetch and turbo-stream. This removes these exports from React Router: (#​11744)

  • defer
  • AbortedDeferredError
  • type TypedDeferredData
  • UNSAFE_DeferredData
  • UNSAFE_DEFERRED_SYMBOL,

• Use createRemixRouter/RouterProvider in entry.client instead of RemixBrowser (#​11469)

• Remove single fetch future flag. (#​11522)

• Remove future.v7_startTransition flag (#​11696)

• Remove future.v7_normalizeFormMethod future flag (#​11697)

• Allow returning undefined from actions and loaders (#​11680)

• update minimum node version to 18 (#​11690)

• Remove future.v7_prependBasename from the ionternalized @remix-run/router package (#​11726)

• Remove future.v7_throwAbortReason from internalized @remix-run/router package (#​11728)

• Add exports field to all packages (#​11675)

• node package no longer re-exports from react-router (#​11702)

• updates the minimum React version to 18 (#​11689)

• • Remove the future.v7_partialHydration flag (#​11725)
    • This also removes the <RouterProvider fallbackElement> prop
      • To migrate, move the fallbackElement to a hydrateFallbackElement/HydrateFallback on your root route
    • Also worth nothing there is a related breaking changer with this future flag:
      • Without future.v7_partialHydration (when using fallbackElement), state.navigation was populated during the initial load
      • With future.v7_partialHydration, state.navigation remains in an "idle" state during the initial load

• Remove future.v7_fetcherPersist flag (#​11731)

Minor Changes

• Add prefetching support to Link/NavLink when using Remix SSR (#​11402)
• Enhance ScrollRestoration so it can restore properly on an SSR'd document load (#​11401)
• Add built-in Remix-style hydration support to RouterProvider. When running from a Remix-SSR'd HTML payload with the proper window variables (__remixContext, __remixManifest, __remixRouteModules), you don't need to pass a router prop and RouterProvider will create the router for you internally. (#​11396) (#​11400)

Patch Changes

• Memoize some RouterProvider internals to reduce uneccesary re-renders (#​11817)
• Updated dependencies:
  • react-router@7.0.0

v6.30.4

Compare Source

v6.30.3

Compare Source

v6.30.2

Compare Source

v6.30.1

Compare Source

v6.30.0

Compare Source

v6.29.0

Compare Source

v6.28.2

Compare Source

v6.28.1

Compare Source

v6.28.0

Compare Source

v6.27.0

Compare Source

v6.26.2

Compare Source

v6.26.1

Compare Source

v6.26.0

Compare Source

v6.25.1

Compare Source

v6.25.0

Compare Source

v6.24.1

Compare Source

v6.24.0

Compare Source

v6.23.1

Compare Source

v6.23.0

Compare Source

v6.22.3

Compare Source

v6.22.2

Compare Source

v6.22.1

Compare Source

v6.22.0

Compare Source

v6.21.3

Compare Source

v6.21.2

Compare Source

v6.21.1

Compare Source

v6.21.0

Compare Source

v6.20.1

Compare Source

v6.20.0

Compare Source

v6.19.0

Compare Source

v6.18.0

Compare Source

v6.17.0

Compare Source

v6.16.0

Compare Source

v6.15.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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 was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @mui/material@5.14.0
npm ERR! Found: @emotion/styled@10.0.27
npm ERR! node_modules/@emotion/styled
npm ERR!   @emotion/styled@"^10.0.17" from @storybook/theming@5.3.21
npm ERR!   node_modules/@storybook/theming
npm ERR!     @storybook/theming@"5.3.21" from @storybook/addon-actions@5.3.21
npm ERR!     node_modules/@storybook/addon-actions
npm ERR!       @storybook/addon-actions@"^5.3.21" from the root project
npm ERR!     @storybook/theming@"5.3.21" from @storybook/addon-info@5.3.21
npm ERR!     node_modules/@storybook/addon-info
npm ERR!       dev @storybook/addon-info@"^5.3.21" from the root project
npm ERR!     2 more (@storybook/api, @storybook/components)
npm ERR!   @emotion/styled@"^10.0.4" from storybook-addon-material-ui@0.9.0-alpha.24
npm ERR!   node_modules/storybook-addon-material-ui
npm ERR!     dev storybook-addon-material-ui@"^0.9.0-alpha.24" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @emotion/styled@"^11.3.0" from @mui/material@5.14.0
npm ERR! node_modules/@mui/material
npm ERR!   dev @mui/material@"^5.14.0" from the root project
npm ERR!   peer @mui/material@"^5.0.0" from @mui/icons-material@5.14.0
npm ERR!   node_modules/@mui/icons-material
npm ERR!     dev @mui/icons-material@"^5.14.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @emotion/styled@11.11.5
npm ERR! node_modules/@emotion/styled
npm ERR!   peerOptional @emotion/styled@"^11.3.0" from @mui/material@5.14.0
npm ERR!   node_modules/@mui/material
npm ERR!     dev @mui/material@"^5.14.0" from the root project
npm ERR!     peer @mui/material@"^5.0.0" from @mui/icons-material@5.14.0
npm ERR!     node_modules/@mui/icons-material
npm ERR!       dev @mui/icons-material@"^5.14.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-23T18_21_10_035Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-23T18_21_10_035Z-debug-0.log

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: react-app@0.1.0
npm error Found: react@17.0.2
npm error node_modules/react
npm error   react@"^17.0.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@">=18" from react-router-dom@7.18.3
npm error node_modules/react-router-dom
npm error   dev react-router-dom@"^7.18.3" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-10T16_52_32_264Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-10T16_52_32_264Z-debug-0.log