Replies: 2 comments
-
ping @Coly010 |
Beta Was this translation helpful? Give feedback.
0 replies
-
No, it's not automatically happening with the Nx will continue to default to the in your export const config: ModuleFederationConfig = {
name: 'myhost',
remotes: [
['remote1', 'http://localhost:4201/mf-manifest.json']
]
} To use the runtime helpers, in your bootstrap file, you can call init({
name: 'myhost',
remotes: [
{
name: 'myremote',
entry: 'http://localhost:4201/mf-manifest.json'
}
]
}) Then wherever you would usually use |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello!
Since NX use
@module-federation/enhanced
, how to actually use the Federation Runtime (https://module-federation.io/guide/basic/runtime.html) ?I want to be able to call
init()
andloadRemote()
. Or is NX doing all this work magically when we callimport()
?Additionnaly, currently NX still load "remote-entry.ts" instead of "mf-manifest.json", and I don't see a way to tell nx to use "mf-manifest.json" instead.
Beta Was this translation helpful? Give feedback.
All reactions