Zack Jackson
Zack Jackson
So the problem here. I think, is the remote container initialization phase. If a host marks it as external the runtime should still register react, and just point to the...
Well if the webpack still registered externals in its api/share scope. Then you could manually specify the version and make the import value be external React That way share scope...
I think it should be reopened, this can cause strange regressions where there doesn't need to be. I believe what would need to change is the SharingRuntimeModule.js Regarding sharing externals...
@vankop @sokra - any ideas on how we can make this happen?
Remote seems to lose its global scope or not inject container at all when umd
Can we get this merged?
What about setting runtime: false on module federation plugin? If you have runtimeChunk: single - it can cause some issues - I've seen similar problems with webpack ESM output when...
@vankop @sokra any ideas here? this looks like a bug in webpack for making worker runtime be an initial chunk
This does seem like a legitimate bug, entry flag should check runtime requirements for runtime globals related to module federation (init, get, share, consume) or chunk loading or if chunk...
Looks good to me but I'll leave it to @evilebottnawi @sokra who are familiar with intersecting running connections