fix(deps): update react-router monorepo to v6.16.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-router	6.15.0 -> 6.16.0
react-router-dom	6.15.0 -> 6.16.0

---

Release Notes

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

v6.16.0

Compare Source

Minor Changes

• In order to move towards stricter TypeScript support in the future, we're aiming to replace current usages of any with unknown on exposed typings for user-provided data. To do this in Remix v2 without introducing breaking changes in React Router v6, we have added generics to a number of shared types. These continue to default to any in React Router and are overridden with unknown in Remix. In React Router v7 we plan to move these to unknown as a breaking change. (#​10843)
  • Location now accepts a generic for the location.state value
  • ActionFunctionArgs/ActionFunction/LoaderFunctionArgs/LoaderFunction now accept a generic for the context parameter (only used in SSR usages via createStaticHandler)
  • The return type of useMatches (now exported as UIMatch) accepts generics for match.data and match.handle - both of which were already set to unknown
• Move the @private class export ErrorResponse to an UNSAFE_ErrorResponseImpl export since it is an implementation detail and there should be no construction of ErrorResponse instances in userland. This frees us up to export a type ErrorResponse which correlates to an instance of the class via InstanceType. Userland code should only ever be using ErrorResponse as a type and should be type-narrowing via isRouteErrorResponse. (#​10811)
• Export ShouldRevalidateFunctionArgs interface (#​10797)
• Removed private/internal APIs only required for the Remix v1 backwards compatibility layer and no longer needed in Remix v2 (_isFetchActionRedirect, _hasFetcherDoneAnything) (#​10715)

Patch Changes

• Updated dependencies:
  • @remix-run/router@1.9.0

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

v6.16.0

Compare Source

Minor Changes

• Updated dependencies:
  • @remix-run/router@1.9.0
  • react-router@6.16.0

Patch Changes

• Properly encode rendered URIs in server rendering to avoid hydration errors (#​10769)

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone America/New_York, 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 has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: frontend-app-ora@0.1.0
npm WARN Found: jest@29.6.4
npm WARN node_modules/jest
npm WARN   dev jest@"29.7.0" from the root project
npm WARN   1 more (jest-when)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer jest@">=26 <27" from ts-jest@26.5.6
npm WARN node_modules/ts-jest
npm WARN   dev ts-jest@"^26.5.6" from the root project
npm WARN   1 more (@formatjs/ts-transformer)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @edx/react-unit-test-utils@1.7.0
npm ERR! Found: @edx/frontend-build@12.9.0-alpha.6
npm ERR! node_modules/@edx/frontend-build
npm ERR!   dev @edx/frontend-build@"12.9.0-alpha.6" from the root project
npm ERR!   peer @edx/frontend-build@">= 8.1.0 || ^12.9.0-alpha.1" from @edx/frontend-platform@5.3.2
npm ERR!   node_modules/@edx/frontend-platform
npm ERR!     @edx/frontend-platform@"5.3.2" from the root project
npm ERR!     peer @edx/frontend-platform@"^4.0.0 || ^5.0.0" from @edx/frontend-component-footer@12.2.1
npm ERR!     node_modules/@edx/frontend-component-footer
npm ERR!       @edx/frontend-component-footer@"12.2.1" from the root project
npm ERR!     1 more (@edx/frontend-component-header)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @edx/frontend-build@">=8.1.0" from @edx/react-unit-test-utils@1.7.0
npm ERR! node_modules/@edx/react-unit-test-utils
npm ERR!   @edx/react-unit-test-utils@"1.7.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @edx/frontend-build@12.9.10
npm ERR! node_modules/@edx/frontend-build
npm ERR!   peer @edx/frontend-build@">=8.1.0" from @edx/react-unit-test-utils@1.7.0
npm ERR!   node_modules/@edx/react-unit-test-utils
npm ERR!     @edx/react-unit-test-utils@"1.7.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/18cd78/86e965/cache/others/npm/_logs/2023-09-18T09_27_51_708Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/18cd78/86e965/cache/others/npm/_logs/2023-09-18T09_27_51_708Z-debug-0.log