ErrorBoundaryProps are empty on client-side in framework mode

[eladchen]

Reproduction

https://stackblitz.com/edit/github-7gefvrqt?file=app%2Froutes%2Fhome.tsx

System Info

System:
    OS: macOS 26.2
    CPU: (10) arm64 Apple M1 Pro
    Memory: 88.52 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.13.0 - /Users/eladchen/.nvm/versions/node/v24.13.0/bin/node
    npm: 11.6.2 - /Users/eladchen/.nvm/versions/node/v24.13.0/bin/npm
  Browsers:
    Chrome: 144.0.7559.133
    Safari: 26.2
  npmPackages:
    @react-router/dev: ^7.5.0 => 7.13.0
    @react-router/express: ^7.5.0 => 7.13.0
    @react-router/node: ^7.5.0 => 7.13.0
    react-router: ^7.5.0 => 7.13.0
    vite: ^7.3.1 => 7.3.1

Used Package Manager

npm

Expected Behavior

props should contain { error, params, loaderData, actionData } as documented and as typed by Route.ErrorBoundaryProps.

The error boundary docs show framework mode using { error }: Route.ErrorBoundaryProps, which implies props are always available.

Actual Behavior

props is {}. The error is only accessible via useRouteError() hook.

useRouteError(), useLoaderData(), useParams(), and useActionData() all work correctly — the issue is only with props injection.

[Axadali]

Hi @eladchen,
Thanks for reporting this issue and providing a detailed reproduction and system information.

I’m planning to start working on this issue. I’ll begin by reproducing the behavior on my side and analyzing why the ErrorBoundary props are not being injected as documented.

In case I need any clarification or additional details, I’ll reach out here.