bundle-stats build(deps-dev): bump react-router-dom from 5.3.4 to 7.6.2

Bumps react-router-dom from 5.3.4 to 7.6.2.

Release notes

Sourced from react-router-dom's releases.

v7.1.3

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

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: "/",

... (truncated)

Changelog

Sourced from react-router-dom's changelog.

7.6.2

Patch Changes

Updated dependencies:

[email protected]

7.6.1

Patch Changes

Updated dependencies:

[email protected]

7.6.0

Patch Changes

Updated dependencies:

[email protected]

7.5.3

Patch Changes

Updated dependencies:

[email protected]

7.5.2

Patch Changes

Updated dependencies:

[email protected]

7.5.1

Patch Changes

Updated dependencies:

[email protected]

7.5.0

Patch Changes

Updated dependencies:

[email protected]

7.4.1

... (truncated)

Commits

49e7664 chore: Update version for release (#13733)
a36c505 chore: Update version for release (#13670)
15087c0 chore: Update version for release (pre) (#13669)
4eb6fd8 chore: Update version for release (pre) (#13653)
ec173d8 chore: Update version for release (pre) (#13637)
8389d48 Update dev dependencies to React 19 (#13558)
c29148e chore: Update version for release (#13561)
3adc571 chore: Update version for release (pre) (#13545)
9a41029 chore: Update version for release (#13482)
945295b chore: Update version for release (pre) (#13479)
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)

Jun 04 '25 02:06 dependabot[bot]

[!IMPORTANT]

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

Jun 04 '25 02:06 coderabbitai[bot]

#12292 Bundle Size — 387.51KiB (+1.38%).

c044560(current) vs bc7ab18 master#12286(baseline)

[!WARNING] Bundle introduced one new package: cookie – View changed packages

[!NOTE] Bundle removed 2 duplicate packages – View changed duplicate packages

Bundle metrics Change

5 changes

1 regression

2 improvements

	Current #12292	Baseline #12286
Initial JS	`339.95KiB`(`+1.57%`)	`334.69KiB`
Initial CSS	`47.56KiB`	`47.56KiB`
Cache Invalidation	`87.56%`	`12.44%`
Chunks	`3`	`3`
Assets	`4`	`4`
Modules	`688`(`-1.85%`)	`701`
Duplicate Modules	`0`	`0`
Duplicate Code	`0%`	`0%`
Packages	`31`(`-20.51%`)	`39`
Duplicate Packages	`0`(`-100%`)	`1`