Zack Jackson

Or we might be able to create new module factories for failures. But let me propose new code losing tools then let's see what we can do about it

I'm not sure of the implications of doing this. Would it mean that any child compilers created would not include any federation stuff unless the plugin is applied again on...

Can we cut a release of this? then i can override the packages in federation examples and we can test against all those as well

yes please!

That's because share scope is omnidirectional and the initialization phase is called by all runtimes who then register what they can offer, none of it loads at that point but...

Here is a solution to it, using runtime plugins: https://github.com/module-federation/module-federation-examples/blob/master/federated-npm/app1/npm-runtime-global-plugin.js https://github.com/module-federation/module-federation-examples/blob/master/federated-npm/app1/webpack.config.js

Do you get a warning in browser like “failed to init external” or something along those lines?

try removing unneeded plugins, try disabling webpack dev server package

@alexander-akait bump

I'm forking module federation so I'll address this during the rebuild. Will try and pr back to webpack but either way should be able to support this soon