You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we were trying to use bridge-react to include a react v19 federated module safely into a react v18 host with react-bridge and react-runtime, we noticed that it does not work. The first reason for this that we can see is that the @module-federation/bridge-react is currently bundling react-dom/client.
This bundling looks accidental to me, so I opened a PR to fix it ( #3476 ).
Reproduction
Check out this repository
build the bridge-react package
check the imports in bridge-react/dist/index.es.js
You will see that there is no import for react-dom/client, instead the code is bundled below containing __SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED on line 333
Describe the bug
When we were trying to use bridge-react to include a react v19 federated module safely into a react v18 host with react-bridge and react-runtime, we noticed that it does not work. The first reason for this that we can see is that the
@module-federation/bridge-react
is currently bundling react-dom/client.This bundling looks accidental to me, so I opened a PR to fix it ( #3476 ).
Reproduction
Check out this repository
build the bridge-react package
check the imports in bridge-react/dist/index.es.js
__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED
on line 333Alternatively to the steps above you can also check the bundle at https://www.npmjs.com/package/@module-federation/bridge-react?activeTab=code and then @module-federation/bridge-react/dist/index.es.js line 333
Used Package Manager
pnpm
System Info
Validations
The text was updated successfully, but these errors were encountered: