Issue when migrating from webpack to enhanced

[einarq]

When trying to switch over a fairly simple repo from webpack plugin to the new one from enhanced I get this error:

I'm using CJS here btw, not sure if that might be related?

I know I should try to create a repro :) Just thinking that maybe there is a common cause for this?

[ Module Federation Manifest Plugin ] Warn Manifest will not generate, because publicPath can only be string, but got 'undefined'
C:\dev\confirmit.components.client\node_modules\@module-federation\enhanced\dist\src\lib\container\runtime\FederationModulesPlugin.js:21
                addContainerEntryModule: new tapable_1.SyncHook(['dependency']),
                                         ^

TypeError: tapable_1.SyncHook is not a constructor
    at FederationModulesPlugin.getCompilationHooks (C:\dev\confirmit.components.client\node_modules\@module-federation\enhanced\dist\src\lib\container\runtime\FederationModulesPlugin.js:21:42)
    at C:\dev\confirmit.components.client\node_modules\@module-federation\enhanced\dist\src\lib\container\ContainerPlugin.js:141:61

[ScriptedAlchemy]

Looks like a issue on my end. Just install tappable for now and that might resolve it. If you have repo that will help too

[ScriptedAlchemy]

no it doesnt, thats just if you want to use the pure runtime for advanced stuff.
Look at the apps, most of them use import from or import()
https://github.com/module-federation/core/tree/main/apps

[einarq]

But with a dynamic location for the remote, unknown at build time.
what we used to solve with promise new promise

[einarq]

I'm looking through these apps, but cannot find any examples of using a dynamic remote unknown remote. Can only find remotes that are set up with localhost.
I mean what we used to solve with either external-remotes-plugin, or later with "promise new Promise".

Isnt that what we should use the new "runtime" helpers for? And hence use loadRemote, instead of import()?

Trying to google the issue is of course not giving great results either, since most are about the "old" module federation.
Stuff like this:
https://dev.to/w3nda/dynamic-remotes-with-modulefederation-67f

Maybe something that deserves a section in the docs? Don't most real world applications of module federation need to solve this?

[ScriptedAlchemy]

you can use registerRemote from federation runtime, you can also use a runtime plugin to dynamically change things. Look at the runtime-plugins folder under module federation example repo

[einarq]

So you're saying that if I use registerRemote, then I can still do this?:

const AppHeader= lazy(() => import('remote/AppHeader'));