fix(react): Update error message for invalid remote name

[ndcunningham]

Current Behavior

Currently, when you have an invalid remote you only get this error.

 >  NX   Cannot read properties of undefined (reading 'data')


TypeError: Cannot read properties of undefined (reading 'data')
    at readCachedProjectConfiguration (/private/tmp/projects/react-mfe/node_modules/nx/src/project-graph/project-graph.js:47:17)
    at /private/tmp/projects/react-mfe/node_modules/@nx/react/src/module-federation/utils.js:11:88
    at handleStringRemote (/private/tmp/projects/react-mfe/node_modules/@nx/webpack/src/utils/module-federation/remotes.js:45:30)
    at mapRemotes (/private/tmp/projects/react-mfe/node_modules/@nx/webpack/src/utils/module-federation/remotes.js:20:37)
    at getModuleFederationConfig (/private/tmp/projects/react-mfe/node_modules/@nx/react/src/module-federation/utils.js:62:25)
    at withModuleFederation (/private/tmp/projects/react-mfe/node_modules/@nx/react/src/module-federation/with-module-federation.js:11:112)
    at Object.<anonymous> (/private/tmp/projects/react-mfe/home/webpack.config.js:15:3)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Object.require.extensions.<computed> [as .js] (/private/tmp/projects/react-mfe/node_modules/ts-node/src/index.ts:1608:43)

Expected Behavior

Have a better error message.

Cannot find project "remoteDoesNotExists". Check that the name is correct in your module-federation config file.

Related Issue(s)

Fixes #

[vercel]

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

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Oct 20, 2023 3:39pm

[nx-cloud]

☁️ Nx Cloud Report

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

---

Sent with 💌 from NxCloud.

[Coly010]

I feel like instead of a try catch, we could just use an if statement to check if the project exists in the graph.

if it does, continue, if it doesn’t, log a warning, but continue execution with the next remote?

Cc @jaysoo

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