chore(deps): update dependency react-router-dom to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-router-dom (source)	6.28.2 -> 7.2.0

---

Release Notes

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

v7.2.0

Compare Source

Patch Changes

• Updated dependencies:
  • [email protected]

v7.1.5

Compare Source

Patch Changes

• Updated dependencies:
  • [email protected]

v7.1.4

Compare Source

Patch Changes

• Updated dependencies:
  • [email protected]

v7.1.3

Compare Source

Patch Changes

• Updated dependencies:
  • [email protected]

v7.1.2

Compare Source

Patch Changes

• Updated dependencies:
  • [email protected]

v7.1.1

Compare Source

Patch Changes

• Updated dependencies:
  • [email protected]

v7.1.0

Compare Source

Patch Changes

• Updated dependencies:
  • [email protected]

v7.0.2

Compare Source

Patch Changes

• Updated dependencies:
  • [email protected]

v7.0.1

Compare Source

Patch Changes

• Updated dependencies:
  • [email protected]

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:
  • [email protected]

v6.29.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" in timezone America/New_York, Automerge - At any time (no schedule defined).

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

♻ 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @edx/[email protected]
npm error Found: [email protected]
npm error node_modules/react-router-dom
npm error   dev react-router-dom@"7.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react-router-dom@"^6.0.0" from @edx/[email protected]
npm error node_modules/@edx/frontend-platform
npm error   dev @edx/frontend-platform@"^8.2.1" from the root project
npm error   peer @edx/frontend-platform@"^7.0.0 || ^8.0.0" from @openedx/[email protected]
npm error   node_modules/@openedx/frontend-plugin-framework
npm error     dev @openedx/frontend-plugin-framework@"^1.5.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react-router-dom
npm error   peer react-router-dom@"^6.0.0" from @edx/[email protected]
npm error   node_modules/@edx/frontend-platform
npm error     dev @edx/frontend-platform@"^8.2.1" from the root project
npm error     peer @edx/frontend-platform@"^7.0.0 || ^8.0.0" from @openedx/[email protected]
npm error     node_modules/@openedx/frontend-plugin-framework
npm error       dev @openedx/frontend-plugin-framework@"^1.5.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error 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/2025-03-03T20_38_17_338Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-03-03T20_38_17_338Z-debug-0.log