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 starting to use module federation with nx and rspack, I analyzed the output of the remotes and I noticed there was quite some boilerplate code between my remotes entries. I discovered that there is a experimental flag provideExternalRuntime for the host and externalRuntime for the remotes https://module-federation.io/configure/experiments.html#externalruntime
However after settings those two flags to true, lots of boilerplate code went out to the host code. However, some runtime code is still remaining in the remote as you can see below.
Do you know why it's happening? Why can some boilerplate be extracted to the host but not the bit above on the screenshot
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.
-
When starting to use module federation with nx and rspack, I analyzed the output of the remotes and I noticed there was quite some boilerplate code between my remotes entries. I discovered that there is a experimental flag
provideExternalRuntime
for the host andexternalRuntime
for the remotes https://module-federation.io/configure/experiments.html#externalruntimeHowever after settings those two flags to
true
, lots of boilerplate code went out to the host code. However, some runtime code is still remaining in the remote as you can see below.Do you know why it's happening? Why can some boilerplate be extracted to the host but not the bit above on the screenshot
Beta Was this translation helpful? Give feedback.
All reactions