feat(module-federation): use nx run-many to build static remotes in parallel

[Coly010]

• feat(angular): use nx run-many to build remotes in parallel
• feat(react): use nx run-many to build remotes in parallel

Current Behavior

We currently spin up a new forked process for every build of a static remote. This impacts resources and memory consumption when there are a lot of remotes in the workspace.

Expected Behavior

We should use nx run-many instead to manage parallel builds of static remotes allowing for users to find the perfect number of parallel processes that they can use to build static remotes locally.

Related Issue(s)

Fixes #

[vercel]

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

Name	Status	Preview	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	Nov 3, 2023 11:31am

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 8b2758e. 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=4dfa45ca244bbe8c9ad2477a188ff9e0d9d84eab --head=8b2758e69e10d579d2a32115a278289bb4ae489e --parallel=1
• nx affected --targets=lint,test,build --base=4dfa45ca244bbe8c9ad2477a188ff9e0d9d84eab --head=8b2758e69e10d579d2a32115a278289bb4ae489e --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=4dfa45ca244bbe8c9ad2477a188ff9e0d9d84eab --head=8b2758e69e10d579d2a32115a278289bb4ae489e
• nx documentation --no-dte
• nx affected -t e2e-macos --parallel=1 --base=4dfa45ca244bbe8c9ad2477a188ff9e0d9d84eab --head=8b2758e69e10d579d2a32115a278289bb4ae489e

---

Sent with 💌 from NxCloud.

[ndcunningham]

Looks fine just not sure what ANSII_CODE_REGEX means.

[Coly010]

It's a regex to find the codes that output certain strings in the terminal in different colors or as bold text.

They aren't being stripped without that regex and therefore matching strings fails because

Successfully ran target build is actually [32mSuccessfully ran target \u001b[1mbuild it just gets rendered correctly in the terminal but the raw output contains them, so doing any kind of equality or lookup fails.

There's a similar util used in our e2e suites

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