Error boundary doesn't work in NextJS when the remote is offline

[plamen-flutter]

Describe the bug

We used [email protected] with pages router and we relied on an error boundary to catch the error generated when a remote is offline.
For example:

This worked fine until we updated to a newer NextJS version (14.2.3). Now the error is being ignored by the error boundary. We have also tried updating to the latest @module-federation/nextjs-mf version as of today (8.8.5), but the issue persists.

Reproduction

Configure a basic application using @module-federation/nextjs-mf with a host and a remote and start only the host application.

Used Package Manager

yarn

System Info

System:
    OS: macOS 15.1.1
    CPU: (10) arm64 Apple M2 Pro
    Memory: 1.99 GB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.0 - ~/.nvm/versions/node/v20.11.0/bin/node
    Yarn: 3.6.1 - /opt/homebrew/bin/yarn
    npm: 10.2.4 - ~/.nvm/versions/node/v20.11.0/bin/npm
  Browsers:
    Chrome: 131.0.6778.109
    Edge: 131.0.2903.86
    Safari: 18.1.1

Validations

• Read the docs.
• Read the common issues list.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Module federation issue and not a framework-specific issue.
• The provided reproduction is a minimal reproducible example of the bug.

[ScriptedAlchemy]

Are you using React.lazy? You can use next/dynamic with federation.

[plamen-flutter]

Are you using React.lazy? You can use next/dynamic with federation.

We are using next/dynamic. Also tried it with React.lazy, but it made no difference.

[ScriptedAlchemy]

use errorLoadRemote hook, you can see the error logged in your browser is from the default runtime plugin for next.
also dont use next/dynamic

https://github.com/module-federation/core/blob/main/packages/nextjs-mf/src/plugins/container/runtimePlugin.ts