Bump react-router-dom from 4.2.2 to 6.15.0

[dependabot]

Bumps react-router-dom from 4.2.2 to 6.15.0.

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

Full Changelog: https://github.com/remix-run/react-router/compare/[email protected]@6.4.4

[email protected]

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.15.0

Minor Changes

• Add's a new redirectDocument() function which allows users to specify that a redirect from a loader/action should trigger a document reload (via window.location) instead of attempting to navigate to the redirected location via React Router (#10705)

Patch Changes

• Fixes an edge-case affecting web extensions in Firefox that use URLSearchParams and the useSearchParams hook. (#10620)
• Do not include hash in useFormAction() for unspecified actions since it cannot be determined on the server and causes hydration issues (#10758)
• Reorder effects in unstable_usePrompt to avoid throwing an exception if the prompt is unblocked and a navigation is performed synchronously (#10687, #10718)
• Updated dependencies:
  • @remix-run/[email protected]
  • [email protected]

6.14.2

Patch Changes

• Properly decode element id when emulating hash scrolling via <ScrollRestoration> (#10682)
• Add missing <Form state> prop to populate history.state on submission navigations (#10630)
• Support proper hydration of Error subclasses such as ReferenceError/TypeError (#10633)
• Updated dependencies:
  • @remix-run/[email protected]
  • [email protected]

6.14.1

Patch Changes

• Updated dependencies:
  • [email protected]
  • @remix-run/[email protected]

6.14.0

Minor Changes

• Add support for application/json and text/plain encodings for useSubmit/fetcher.submit. To reflect these additional types, useNavigation/useFetcher now also contain navigation.json/navigation.text and fetcher.json/fetcher.text which include the json/text submission if applicable (#10413)

  // The default behavior will still serialize as FormData
  function Component() {
    let navigation = useNavigation();
    let submit = useSubmit();
    submit({ key: "value" }, { method: "post" });
    // navigation.formEncType => "application/x-www-form-urlencoded"
    // navigation.formData    => FormData instance
  }

... (truncated)

Commits

• e79cb77 chore: Update version for release (#10776)
• cd1e25a chore: Update version for release (pre) (#10771)
• d6d0e5b Merge branch 'main' into release-next
• fb70fed Do not include hash in useFormAction() for unspecified actions (#10758)
• 46806a4 Add support to force reload on redirect with X-Remix-Reload-Document header...
• b23d7b5 Fix docs on NavLink w.r.t. links to the root route and the end prop (#10757)
• 4bdd6b4 Add setTimeout back to unstable_usePrompt (#10718)
• 78ef4ef Stabilize useRevalidator (#10707)
• 172bad7 Merge branch 'release-next' into dev
• 1acea8b chore: Update version for release (#10711)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[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.