Zack Jackson
Zack Jackson
@sokra in that other pr, the root issue was as follows. the RemoteRuntimeModule constructs its map from the config, and that requires "sharescope" to be set in the build config....
Sure thing, doing it now!
you need to clear require cache. look at the hot-reload functions in module-federation/node package
Look at dynamic node examples in federation examples otherwise dig through the nextjs code and you can see how it's implemented. Or run app in worker thread and each invocation...
It'll take some time to get around to looking at that example again. But in general nuking the require cache should do it and resetting federation globals
@2heal1 some exposed modules may be small or may be critical and he wants to avoid additional network call. Basically like how shared eager=true works, but for exposes. So eager...
The problem with eager module loading will be that you lose the async boundary - if eager expose needs react for example - it will fail since react is not...
If you have an idea of how to add it. Then let's take a look.
Why do you need types generated beforehand? The build should pull the types ahead of time already, and re-pull them each time to sync it per build update (like hmr)
Usually it should wait for type sync before attempting to build. Do you have a repo I can look at?