Native Federation support different federation.config.ts per build configuration

[shastaxc]

For which library do you have a feature request?

native-federation

Information

The Native Federation config file is expected to be federation.config.ts at all times, but it would be helpful to be able to specify a different file to use for different Angular build configurations, such as having a production build use federation-prod.config.ts.

Describe any alternatives/workarounds you're currently using

No current workaround. This is a blocker for my transition from Module Federation to Native Federation (among other blockers).

I would be willing to submit a PR to fix this issue

• Yes
• No

[jmleep]

This is also something that I feel is required for using this package. I also can't seem to use it with environments. As soon as I try to run a build with a configuration flag it fails.

This is just creating a new Angular app, adding the add @angular-architects/native-federation schematic, and then adding environments.

ng build --configuration development
An unhandled exception occurred: Cannot read properties of undefined (reading 'split')

---

Edit:
Actually it looks like my build issue might be fixed in this PR

I still think this is needed for any enterprise/production level app. I think most MFE systems would probably need to point to different MFE application urls depending on local, staging environments, prod, etc.