build(deps): bump react-router from 7.18.4 to 8.4.0 in /web

[dependabot]

Bumps react-router from 7.18.4 to 8.4.0.

Release notes

Sourced from react-router's releases.

v8.4.0

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v840

v8.3.1

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v831

v8.3.0

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v830

v8.2.0

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v820

v8.1.0

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v810

v8.0.1

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v801

v8.0.0

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v800

Changelog

Sourced from react-router's changelog.

v8.4.0

Minor Changes

• Deprecate the createStaticRouter({ branches }) option (#15297)
  • createStaticRouter now caches route branches internally, ignores branches, and logs a deprecation warning when the option is provided
  • The deprecated EntryContext.branches property remains available for compatibility but is always an empty array

Patch Changes

• Prevent stale route discovery during manifest version-mismatch recovery (#15489)
  • Keep concurrent manifest responses pending while a document reload is in progress
  • Report a discovery error when a previous reload failed to resolve a version mismatch instead of loading a stale route or reloading repeatedly
  • Fail pending requests if a document reload does not complete within five seconds or the document is restored from the back-forward cache, allowing subsequent requests to recover
• Preserve lazy route module import errors during SPA navigations instead of replacing them with a missing dataStrategy result error (#15464)
• Switch to more granular internal router contexts to avoid unnecessary route component re-renders when unrelated data router state changes (#15376)
  • ⚠️ This contains some breaking changes to exported UNSAFE_ contexts, so please review carefully if you are using those unsafe exports
• Correctly escape streamed RSC redirect locations in meta tag attributes (#15491)
• Avoid unintended document.startViewTransition calls during initial hydration and router.revalidate() calls (#15484)
• Fix SingleFetchNoResultError thrown when a fetcher revalidates against a splat route during lazy route discovery (#15395)
  • Track discovery per fetcher load so revalidation waits for the current load's discovery, even when the fetcher key is reused, while still restarting interrupted loaders after discovery completes
• Preserve the underlying decode failure as the cause of the Unable to decode turbo-stream response error (#15450)

Unstable Changes

⚠️ Unstable features are not recommended for production use

• Add a Data Mode future.unstable_routePatternMatching flag for more efficient route matching powered by @remix-run/route-pattern (#15298)
  • Add an unstable_validateParams route field to reject invalid parameter values and continue matching
• Document access control requirements for RSC Server Functions (#15490)
  • Treat every Server Function as a public endpoint that must perform all of its own access control checks
  • Recommend route actions when access control should be provided by route middleware

v8.3.1

Patch Changes

• Fix Expected fetcher: <key> error thrown on navigation when a fetcher is aborted during its post-action revalidation (#15365)
• Fix lazy route discovery caching a path as discovered when the triggering navigation was aborted after the manifest response settled but before the route tree was patched, which permanently (for the session) shadowed the real route behind a catch-all or produced 404s on every subsequent visit (#15399)
• Improve route matching performance for long paths (#15417)
• Improve validation of action request origins (#15419)
• Fix <ScrollRestoration> leaving history.scrollRestoration set to "auto" after a bfcache restore, which let the browser restore scroll on subsequent history traversals before the destination route had rendered (#15397)
• Properly respect the relative option in useSubmit/fetcher.submit when resolivng the action path (#15400)
• Add additional URL validation on client side navigations/redirects (#15445)

v8.3.0

Patch Changes

• Encode path params in href/generatePath per RFC 3986 path-segment rules instead of encodeURIComponent (#15310)

... (truncated)

Commits

• 7ccdcec Release v8.4.0 (#15496)
• dc95459 Prepare v8.4.0 release notes
• 5fe40ed Fix change file
• f329d4b Skip view transitions on revalidation and initial hydration (#15484)
• 34ffffb Preload the route-pattern matcher before opting in (#15506)
• 4091c34 Document RSC server function access control (#15490)
• 6f2a0e0 Restore upstream route-pattern dependency (#15505)
• 10908b2 docs: fix router comment spelling (#15495)
• acf1f20 Fix empty terminating splats with route-pattern matching (#15499)
• c58d715 Fix HTML attribute escaping for RSC redirects (#15491)
• Additional commits viewable in compare view

[Sulaiman-Dauda]

Superseded by #58, which moves React, Vite and React Router together so the peer dependencies line up.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.