feat(react): Add federate-module generator

[ndcunningham]

This PR contains

A federate module generator which should do a few things:

Command

nx generate @nx/react:federate-module Carosel --path=carosel/src/lib/carosel --remote=ui

1. It will generate/update a remote adding a path to a module provided to the generator
2. Update if existing the module-federation.config.js to add a new entry to the exposes property for the new module

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	Oct 6, 2023 5:26pm

[nx-cloud]

☁️ Nx Cloud Report

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

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 6 targets

• nx affected --target=e2e --base=e97bbc040b3c0e31b4ac54c8f0839e56daaec1cb --head=6f952dbdfd088fd10feabba7ef5661719f94e09f --parallel=1
• nx affected --targets=lint,test,build --base=e97bbc040b3c0e31b4ac54c8f0839e56daaec1cb --head=6f952dbdfd088fd10feabba7ef5661719f94e09f --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=e97bbc040b3c0e31b4ac54c8f0839e56daaec1cb --head=6f952dbdfd088fd10feabba7ef5661719f94e09f
• nx documentation --no-dte
• nx affected -t e2e-macos --parallel=1 --base=e97bbc040b3c0e31b4ac54c8f0839e56daaec1cb --head=6f952dbdfd088fd10feabba7ef5661719f94e09f

---

Sent with 💌 from NxCloud.

[Coly010]

Looks great!

i think there are a couple of things missing.

When we add the federated module, we should also add a path alias to the root tsconfig file following the same format.

”remote-app/MyModule”: [“./path/to/file”]

The only other things I’d love to have relate to testing.

1. can we test an integrated repo, where the lib is a separate project? The remote could be in apps/ but the file we want to federate is in libs/ - perhaps we should update the description on the path flag in the schema to mention workspace root.
   You can see an example of where I’ve done this in an Angular app: https://github.com/Coly010/mf-federated-service-example/blob/main/apps/auth-remote/module-federation.config.js

2. It would be great if our e2es tested federating a path, and then having that path be consumed in the host, and ensuring that build works and when served, the content of the federated module renders correctly.

i think the e2es you have currently which check if the files exist etc could become unit tests.

but overall this is awesome! 🎉 great work

[Coly010]

One typo, but otherwise this looks great! 🎉

This is an exciting feature to have!

[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.