Bump react-router from 7.8.1 to 7.9.4

[dependabot]

Bumps react-router from 7.8.1 to 7.9.4.

Release notes

Sourced from react-router's releases.

v7.9.4

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

v7.9.3

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

v7.9.2

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

v7.9.1

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

v7.9.0

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

v7.8.2

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

Changelog

Sourced from react-router's changelog.

7.9.4

Patch Changes

• handle external redirects in from server actions (#14400)

• New (unstable) useRoute hook for accessing data from specific routes (#14407)

  For example, let's say you have an admin route somewhere in your app and you want any child routes of admin to all have access to the loaderData and actionData from admin.

  // app/routes/admin.tsx
  import { Outlet } from "react-router";
  export const loader = () => ({ message: "Hello, loader!" });
  export const action = () => ({ count: 1 });
  export default function Component() {
  return (
  <div>
  {/* ... /}
  <Outlet />
  {/ ... */}
  </div>
  );
  }

  You might even want to create a reusable widget that all of the routes nested under admin could use:

  import { unstable_useRoute as useRoute } from "react-router";
  export function AdminWidget() {
  // How to get message and count from admin route?
  }

  In framework mode, useRoute knows all your app's routes and gives you TS errors when invalid route IDs are passed in:

  export function AdminWidget() {
    const admin = useRoute("routes/dmin");
    //                      ^^^^^^^^^^^
  }

  useRoute returns undefined if the route is not part of the current page:

... (truncated)

Commits

• e650acf chore: Update version for release (#14431)
• 7a2271e chore: Update version for release (pre) (#14427)
• f46c83c Merge branch 'main' into release-next
• 45bad2b unstable_useRoute (#14407)
• 19ac8db fix(docs): correct unclosed Route tag in JSX example (#14406)
• 850bf9a fix: handle rsc external redirects (#14400)
• 2b592a3 chore: format
• 4ec4999 chore: format
• 12a6719 chore: Update version for release (#14395)
• b6c49ec chore: Update version for release (pre) (#14394)
• 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)

[bert-e]

Hello dependabot[bot],

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

The following options are set: bypass_author_approval, bypass_jira_check

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• one peer

Peer approvals must include at least 1 approval from the following list:

• @ChengYanJin

• @MonPote

• @damiengillesscality

• @hervedombya

• @JBWatenbergScality

The following options are set: bypass_author_approval, bypass_jira_check

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• one peer

Peer approvals must include at least 1 approval from the following list:

• @damiengillesscality

• @JBWatenbergScality

• @hervedombya

• @ChengYanJin

• @MonPote

The following options are set: bypass_author_approval, bypass_jira_check

[bert-e]

Conflict

There is a conflict between your branch dependabot/npm_and_yarn/react-router-7.9.4 and the
destination branch development/4.1.

Please resolve the conflict on the feature branch (dependabot/npm_and_yarn/react-router-7.9.4).

git fetch && \
git checkout origin/dependabot/npm_and_yarn/react-router-7.9.4 && \
git merge origin/development/4.1

Resolve merge conflicts and commit

git push origin HEAD:dependabot/npm_and_yarn/react-router-7.9.4

The following options are set: bypass_author_approval, bypass_jira_check

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• one peer

Peer approvals must include at least 1 approval from the following list:

• @ChengYanJin

• @JBWatenbergScality

• @damiengillesscality

• @hervedombya

• @MonPote

The following options are set: bypass_author_approval, bypass_jira_check

[dependabot]

Superseded by #975.