Open joon84 opened 3 weeks ago
Have you tried migrating to native-federation
via the docs here: https://github.com/angular-architects/module-federation-plugin/blob/main/libs/native-federation/docs/migrate.md
The new plugin uses esbuild.
Have you tried migrating to
native-federation
via the docs here: https://github.com/angular-architects/module-federation-plugin/blob/main/libs/native-federation/docs/migrate.mdThe new plugin uses esbuild.
hi, our shell/ host uses module-federation.
and remote/ mfe is angular based, we tried with native-foundation in remote/ mfe side as well. but "module-federated" host cannot consume "native-federated" remote (they are not compatible it seems, e.g. native-foundation uses browser technology like importMaps etc ) ..
Did you try using Angular native-federation for both the host and the remote?
Did you try using Angular native-federation for both the host and the remote?
we have not tried it, since our organization decided the shell/ host will be react based and will have module federation.
that means, we need to allow only module-federated remotes/ mfes.. for angular ones, there are waysto do that.. but have not found a good way to do that with esbuild for angular remotes... ppl are working on that it seems, but if anything working available by now, it will be a great input and help
Hello. Is there any plan for upgrading or making new changes to existing "@angular-architects/module-federation" to support esbuild?
The latest "@angular-devkit/build-angular" builders are moving towards esbuild. And lacking the extra config file options like we can have one with "@angular-builders/custom-webpack" or so.
Use case: for us, our host is react based (prefering "module-federation" with rspack/ webpack), and remotes/ mfes are mostly angular based where esbuild is hot topic.
Warm regards