chore(deps): update react-router monorepo to v7.9.3

[renovate]

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.

---

This PR contains the following updates:

Package	Change	Age	Confidence
@react-router/cloudflare (source)	7.9.1 -> 7.9.3
@react-router/dev (source)	7.9.1 -> 7.9.3
@react-router/fs-routes (source)	7.9.1 -> 7.9.3
react-router (source)	7.9.1 -> 7.9.3

---

Release Notes

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

v7.9.3

Compare Source

Patch Changes

• Updated dependencies:
  • [email protected]

v7.9.2

Compare Source

Patch Changes

• Updated dependencies:
  • [email protected]

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

v7.9.3

Compare Source

Patch Changes

• Updated dependencies:
  • [email protected]
  • @react-router/[email protected]
  • @react-router/[email protected]

v7.9.2

Compare Source

Patch Changes

• Fix preset future flags being ignored during config resolution (#​14369)

  Fixes a bug where future flags defined by presets were completely ignored. The config resolution was incorrectly reading from reactRouterUserConfig.future instead of the merged userAndPresetConfigs.future, causing all preset-defined future flags to be lost.

  This fix ensures presets can properly enable experimental features as intended by the preset system design.

• Add unstable support for RSC Framework Mode (#​14336)

• Switch internal vite plugin Response logic to use @remix-run/node-fetch-server (#​13927)

• Updated dependencies:

  • [email protected]
  • @react-router/[email protected]
  • @react-router/[email protected]

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

v7.9.3

Compare Source

Patch Changes

• Updated dependencies:
  • @react-router/[email protected]

v7.9.2

Compare Source

Patch Changes

• Updated dependencies:
  • @react-router/[email protected]

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

v7.9.3

Compare Source

Patch Changes

• Do not try to use turbo-stream to decode CDN errors that never reached the server (#​14385)

  • We used to do this but lost this check with the adoption of single fetch

• Fix Data Mode regression causing a 404 during initial load in when middleware exists without any loader functions (#​14393)

v7.9.2

Compare Source

Patch Changes

• • Update client-side router to run client middleware on initial load even if no loaders exist (#​14348)
  • Update createRoutesStub to run route middleware
    • You will need to set the <RoutesStub future={{ v8_middleware: true }} /> flag to enable the proper context type

• Update Lazy Route Discovery manifest requests to use a singular comma-separated paths query param instead of repeated p query params (#​14321)

  • This is because Cloudflare has a hard limit of 100 URL search param key/value pairs when used as a key for caching purposes
  • If more that 100 paths were included, the cache key would be incomplete and could produce false-positive cache hits

• [UNSTABLE] Add fetcher.unstable_reset() API (#​14206)

• Made useOutlet element reference have stable identity in-between route chages (#​13382)

• feat: enable full transition support for the rsc router (#​14362)

• In RSC Data Mode, handle SSR'd client errors and re-try in the browser (#​14342)

• Support middleware prop on <Route> for usage with a data router via createRoutesFromElements (#​14357)

• Handle encoded question mark and hash characters in ancestor splat routes (#​14249)

• Fail gracefully on manifest version mismatch logic if sessionStorage access is blocked (#​14335)

---

Configuration

📅 Schedule: Branch creation - "before 3am" in timezone Asia/Tokyo, 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 these updates again.

---

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

---

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