Bump react-router-dom from 5.2.0 to 6.8.2 in /frontend

[dependabot]

Bumps react-router-dom from 5.2.0 to 6.8.2.

Release notes

Sourced from react-router-dom's releases.

v6.4.4

What's Changed

• Throw an error if an action/loader function returns undefined as revalidations need to know whether the loader has previously been executed. undefined also causes issues during SSR stringification for hydration. You should always ensure your loader/action returns a value, and you may return null if you don't wish to return anything. (#9511)
• Properly handle redirects to external domains (#9590, #9654)
• Preserve the HTTP method on 307/308 redirects (#9597)
• Support basename in static data routers (#9591)
• Enhanced ErrorResponse bodies to contain more descriptive text in internal 403/404/405 scenarios
• Fix issues with encoded characters in NavLink and descendant <Routes> (#9589, #9647)
• Properly serialize/deserialize ErrorResponse instances when using built-in hydration (#9593)
• Support basename in static data routers (#9591)
• Updated dependencies:
  • @remix-run/router@1.0.4
  • react-router@6.4.4

Full Changelog: https://github.com/remix-run/react-router/compare/react-router-dom@6.4.3...react-router-dom@6.4.4

react-router-dom@6.4.0-pre.15

Patch Changes

• fix: remove internal router singleton (#9227)

  This change removes the internal module-level routerSingleton we create and maintain inside our data routers since it was causing a number of headaches for non-simple use cases:

  • Unit tests are a pain because you need to find a way to reset the singleton in-between tests
    • Use use a _resetModuleScope singleton for our tests
    • ...but this isn't exposed to users who may want to do their own tests around our router
  • The JSX children <Route> objects cause non-intuitive behavior based on idiomatic react expectations
    • Conditional runtime <Route>'s won't get picked up
    • Adding new <Route>'s during local dev won't get picked up during HMR
    • Using external state in your elements doesn't work as one might expect (see #9225)

  Instead, we are going to lift the singleton out into user-land, so that they create the router singleton and manage it outside the react tree - which is what react 18 is encouraging with useSyncExternalStore anyways! This also means that since users create the router - there's no longer any difference in the rendering aspect for memory/browser/hash routers (which only impacts router/history creation) - so we can get rid of those and trim to a simple RouterProvider

  // Before
  function App() {
    <DataBrowserRouter>
      <Route path="/" element={<Layout />}>
        <Route index element={<Home />}>
      </Route>
    <DataBrowserRouter>
  }
  // After
  let router = createBrowserRouter([{
  path: "/",
  element: <Layout />,
  children: [{
  index: true,

... (truncated)

Changelog

Sourced from react-router-dom's changelog.

6.8.2

Patch Changes

• Treat same-origin absolute URLs in <Link to> as external if they are outside of the router basename (#10135)
• Fix useBlocker to return IDLE_BLOCKER during SSR (#10046)
• Fix SSR of absolute <Link to> urls (#10112)
• Properly escape HTML characters in StaticRouterProvider serialized hydration data (#10068)
• Updated dependencies:
  • @remix-run/router@1.3.3
  • react-router@6.8.2

6.8.1

Patch Changes

• Improved absolute url detection in Link component (now also supports mailto: urls) (#9994)
• Fix partial object (search or hash only) pathnames losing current path value (#10029)
• Updated dependencies:
  • react-router@6.8.1
  • @remix-run/router@1.3.2

6.8.0

Minor Changes

• Support absolute URLs in <Link to>. If the URL is for the current origin, it will still do a client-side navigation. If the URL is for a different origin then it will do a fresh document request for the new origin. (#9900)

  <Link to="https://neworigin.com/some/path">    {/* Document request */}
  <Link to="//neworigin.com/some/path">          {/* Document request */}
  <Link to="https://www.currentorigin.com/path"> {/* Client-side navigation */}

Patch Changes

• Fix bug with search params removal via useSearchParams (#9969)
• Respect preventScrollReset on <fetcher.Form> (#9963)
• Fix navigation for hash routers on manual URL changes (#9980)
• Use pagehide instead of beforeunload for <ScrollRestoration>. This has better cross-browser support, specifically on Mobile Safari. (#9945)
• Updated dependencies:
  • @remix-run/router@1.3.1
  • react-router@6.8.0

6.7.0

Minor Changes

• Add unstable_useBlocker hook for blocking navigations within the app's location origin (#9709)
• Add unstable_usePrompt hook for blocking navigations within the app's location origin (#9932)

... (truncated)

Commits

• c312eaa chore: Update version for release (#10142)
• b1aa838 chore: Update version for release (pre) (#10137)
• d43e1ab fix: treat absolute/same-origin/different-basename <Link to> values as extern...
• 1d2417b chore: Update version for release (pre) (#10129)
• d6af011 chore: Update version for release (pre) (#10128)
• 8975de9 Hotfix: absolute URLs on server router (#10112)
• 3c6fb46 chore: Update version for release (pre) (#10124)
• 3eac3a6 feat: mutable route tree (#9996)
• bbe4ec5 Move invariant to UNSAFE_ export (#10066)
• 5706fbd __staticRouterHydrationData html tag escape (#10068)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)