Bump react-router-dom from 6.4.3 to 6.9.0 in /webapp

Bumps react-router-dom from 6.4.3 to 6.9.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/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-v5-compat@6.4.0-pre.15

Patch Changes

Updated dependencies

react-router@6.4.0-pre.15

react-router-dom@6.4.0-pre.15

react-router-dom-v5-compat@6.4.0-pre.11

Patch Changes

Updated dependencies

react-router@6.4.0-pre.11

react-router-dom@6.4.0-pre.11

react-router-dom-v5-compat@6.4.0-pre.10

Patch Changes

Updated dependencies

react-router@6.4.0-pre.10

react-router-dom@6.4.0-pre.10

react-router-dom-v5-compat@6.4.0-pre.9

Patch Changes

Updated dependencies

react-router@6.4.0-pre.9

react-router-dom@6.4.0-pre.9

react-router-dom-v5-compat@6.4.0-pre.8

Patch Changes

Updated dependencies

react-router@6.4.0-pre.8

... (truncated)

Changelog

Sourced from react-router-dom's changelog.

6.9.0

Minor Changes
React Router now supports an alternative way to define your route element and errorElement fields as React Components instead of React Elements. You can instead pass a React Component to the new Component and ErrorBoundary fields if you choose. There is no functional difference between the two, so use whichever approach you prefer 😀. You shouldn't be defining both, but if you do Component/ErrorBoundary will "win". (#10045)

Example JSON Syntax
// Both of these work the same:
const elementRoutes = [{
  path: '/',
  element: <Home />,
  errorElement: <HomeError />,
}]
const componentRoutes = [{
path: '/',
Component: Home,
ErrorBoundary: HomeError,
}]
function Home() { ... }
function HomeError() { ... }
Example JSX Syntax
// Both of these work the same:
const elementRoutes = createRoutesFromElements(
  <Route path='/' element={<Home />} errorElement={<HomeError /> } />
);
const componentRoutes = createRoutesFromElements(
<Route path='/' Component={Home} ErrorBoundary={HomeError} />
);
function Home() { ... }
function HomeError() { ... }
Introducing Lazy Route Modules! (#10045)

In order to keep your application bundles small and support code-splitting of your routes, we've introduced a new lazy() route property. This is an async function that resolves the non-route-matching portions of your route definition (loader, action, element/Component, errorElement/ErrorBoundary, shouldRevalidate, handle).

Lazy routes are resolved on initial load and during the loading or submitting phase of a navigation or fetcher call. You cannot lazily define route-matching properties (path, index, children) since we only execute your lazy route functions after we've matched known routes.

Your lazy functions will typically return the result of a dynamic import.

... (truncated)

Commits

4ec107a chore: Update version for release (#10185)
12db33a chore: Update version for release (pre) (#10174)
c56d84c Lazy Loaded Route Modules (#10045)
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)
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)