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
I didn't have the async boundary option before (because i have multiple entrypoints in my webpack config), but I also tried adding the experimental asyncStartup flag, but the result is the same.
I've spent a lot of time debugging because of this issue. I'd be very grateful if someone could offer to help me with my problem.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm upgrading module federation to V2 (I was previously using webpack.container.ModuleFederationPlugin)
"webpack": "5.94.0",In an attempt to identify the problem, I found the source and cause of this error.
My MF config, when I was using webpack, looked like this:
config ModuleFederation V2 now:
according to https://module-federation.io/guide/debug/variables#share
But my runtime code hasn't changed; the mf code contains this function:
The "eager" field is missing from the "versions[version].eager" line in the new config; it's now in shareConfig.
My config:
I didn't have the async boundary option before (because i have multiple entrypoints in my webpack config), but I also tried adding the experimental asyncStartup flag, but the result is the same.
I've spent a lot of time debugging because of this issue. I'd be very grateful if someone could offer to help me with my problem.
Beta Was this translation helpful? Give feedback.
All reactions