feat(angular): add dynamic federation support to mfe generator

[Coly010]

Current Behavior

Our generators currently have no method of generating a Module Federation setup that uses Dynamic Federation.

Expected Behavior

Our setup-mfe generator should support creating a Dynamic Federation setup.

Only host apps really need to understand the concept of Dynamic Federation as it is within the host app that the wiring of the remote apps takes place.

We want to promote a Dynamic Federation pattern that consists of:

• Build once, deploy anywhere strategy
• A host application that resolves its remotes' locations at runtime
• A JSON file with a structure of: Record<string, string> matching: remoteName: remoteUrl
• A method of fetching the JSON file at runtime to initialise the remote containers.
• A method for routing to the module exposed by the remote apps

Therefore we should aim to achieve 3 things:

• setup-mfe should be able to create a host app with a pattern for dynamic federation
• host generator should have a --dynamic flag that will specify that the host should be created following the dynamic federation pattern
• remote generator should NOT have a --dynamic flag, as it makes no sense for a remote itself. HOWEVER, the logic of adding the remote to a specified --host SHOULD still take into account if the host app has been configured with dynamic federation in mind.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 5c37b61. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 8 targets

• nx affected --target=e2e --base=d33a34105f6ac5808524a1d438161f8bde78c60d --head=5c37b61abe3b11f93f85e79245143f613f1dfbbe --exclude=e2e-storybook,e2e-react-native,e2e-detox --parallel=1
• nx run-many --target=build --all --parallel=8 --exclude=docs,nx-dev-data-access-documents,nx-dev-e2e,nx-dev,nx-dev-feature-analytics,nx-dev-feature-conf,nx-dev-feature-doc-viewer,nx-dev-feature-search,nx-dev-feature-storage,nx-dev-feature-versions-and-flavors,nx-dev-ui-commands,nx-dev-ui-common,nx-dev-ui-home,nx-dev-ui-member-card,nx-dev-ui-sponsor...
• nx run-many --target=build --all --parallel=8 --exclude=docs,nx-dev-data-access-documents,nx-dev-e2e,nx-dev,nx-dev-feature-analytics,nx-dev-feature-conf,nx-dev-feature-doc-viewer,nx-dev-feature-search,nx-dev-feature-storage,nx-dev-feature-versions-and-flavors,nx-dev-ui-commands,nx-dev-ui-common,nx-dev-ui-home,nx-dev-ui-member-card,nx-dev-ui-sponsor...
• nx run-many --target=build --all --parallel=8 --exclude=docs,nx-dev-data-access-documents,nx-dev-e2e,nx-dev,nx-dev-feature-analytics,nx-dev-feature-conf,nx-dev-feature-doc-viewer,nx-dev-feature-search,nx-dev-feature-storage,nx-dev-feature-versions-and-flavors,nx-dev-ui-commands,nx-dev-ui-common,nx-dev-ui-home,nx-dev-ui-member-card,nx-dev-ui-sponsor...
• nx affected --target=test --base=d33a34105f6ac5808524a1d438161f8bde78c60d --head=5c37b61abe3b11f93f85e79245143f613f1dfbbe --parallel=1
• nx affected --target=build --base=d33a34105f6ac5808524a1d438161f8bde78c60d --head=5c37b61abe3b11f93f85e79245143f613f1dfbbe --parallel=3
• nx affected --target=lint --base=d33a34105f6ac5808524a1d438161f8bde78c60d --head=5c37b61abe3b11f93f85e79245143f613f1dfbbe --parallel=3
• nx build typedoc-theme

---

Sent with 💌 from NxCloud.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nrwl/nx-dev/9ttFPzVhihDWFaSq4qxN6o37pChM
✅ Preview: https://nx-dev-git-fork-coly010-angular-dynamic-federation-nrwl.vercel.app

[leosvelperez]

LGTM! 🎉

[jaysoo]

Maybe mention mfe.manfest.json as well in case the user meant to use dynamic host -- maybe they renamed the file without realizing the problem.

Can we do some validation on mfe.config.js to guard on this edge case? i.e. that the host should be using dynamic remotes, but the dynamic manifest isn't found.

[jaysoo]

Looks good overall.

There is an edge case where the user may rename the config files (mfe.config.js and mfe.manifest.json), and it's not obvious that this will cause minor issues later when generating new remotes.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.