Bump react-router from 7.4.0 to 7.5.0

[dependabot]

Bumps react-router from 7.4.0 to 7.5.0.

Release notes

Sourced from react-router's releases.

v7.5.0

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

v7.4.1

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

Changelog

Sourced from react-router's changelog.

7.5.0

Minor Changes

• Add granular object-based API for route.lazy to support lazy loading of individual route properties, for example: (#13294)

  createBrowserRouter([
    {
      path: "/show/:showId",
      lazy: {
        loader: async () => (await import("./show.loader.js")).loader,
        action: async () => (await import("./show.action.js")).action,
        Component: async () => (await import("./show.component.js")).Component,
      },
    },
  ]);

  Breaking change for route.unstable_lazyMiddleware consumers

  The route.unstable_lazyMiddleware property is no longer supported. If you want to lazily load middleware, you must use the new object-based route.lazy API with route.lazy.unstable_middleware, for example:

  createBrowserRouter([
    {
      path: "/show/:showId",
      lazy: {
        unstable_middleware: async () =>
          (await import("./show.middleware.js")).middleware,
        // etc.
      },
    },
  ]);

Patch Changes

• Introduce unstable_subResourceIntegrity future flag that enables generation of an importmap with integrity for the scripts that will be loaded by the browser. (#13163)

7.4.1

Patch Changes

• Fix types on unstable_MiddlewareFunction to avoid type errors when a middleware doesn't return a value (#13311)

• Dedupe calls to route.lazy functions (#13260)

• Add support for route.unstable_lazyMiddleware function to allow lazy loading of middleware logic. (#13210)

  Breaking change for unstable_middleware consumers

... (truncated)

Commits

• 15e0a5e chore: Update version for release (#13366)
• e6630c6 chore: Update version for release (pre) (#13355)
• 57873d1 Use granular route.lazy for loaders/actions (#13339)
• 3aea1f2 chore: Update version for release (pre) (#13345)
• b8cf1b6 chore: format
• 5461461 feat: unstable_subResourceIntegrity (#13163)
• d07cefe Add lazy route property API, use for loading middleware (#13294)
• 7350eef chore: Update version for release (#13322)
• 9693bf4 chore: Update version for release (pre) (#13312)
• b48d1b4 Merge branch 'main' into release-next
• 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)

[changeset-bot]

⚠️ No Changeset found

Latest commit: ffaf26b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR