fix(core): handle falsy error in params.ts#handleErrors

[gioragutt]

Current Behavior

This happens to me when I run a node application and some error happens. The documented log I have is from when I Ctrl+Ced the app, but I've seen this before many times.

$ nx serve cli --watch=false

> nx run cli:serve --watch=false

chunk (runtime: main) main.js (main) 65.6 KiB [entry] [rendered]
chunk (runtime: worker) worker.js (worker) 64.2 KiB [entry] [rendered]
webpack compiled successfully (07835d0c74e6b24a)
Starting inspector on localhost:9229 failed: address already in use
[Nest] 51175  - 05/29/2022, 6:43:52 PM     LOG [NestFactory] Starting Nest application...
[Nest] 51175  - 05/29/2022, 6:43:52 PM     LOG [InstanceLoader] MongooseModule dependencies initialized +47ms
[Nest] 51175  - 05/29/2022, 6:44:22 PM   ERROR [MongooseModule] Unable to connect to the database. Retrying (1)...
^C
Unexpected error                                                                                               
TypeError: Cannot read properties of undefined (reading 'constructor')
    at /path/to/project/node_modules/nx/src/utils/params.js:12:21
    at Generator.throw (<anonymous>)
    at rejected (/path/to/project/node_modules/nx/node_modules/tslib/tslib.js:116:69)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

Expected Behavior

There shouldn't be any uncaught errors within NX's internals

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 983eb55. 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 12 targets

• nx affected --target=build --base=7418ae19c2b32f378a302508df688250017b641c --head=983eb555478caa3a0090a2217b544cf649145dc2 --parallel=3
• nx affected --target=e2e --base=7418ae19c2b32f378a302508df688250017b641c --head=983eb555478caa3a0090a2217b544cf649145dc2 --exclude=e2e-detox,e2e-js,e2e-next,e2e-workspace-create,e2e-workspace-integrations,e2e-workspace-core,e2e-react,e2e-web,e2e-angular-extensions,e2e-angular-core,e2e-cli,e2e-nx-plugin,e2e-cypress,e2e-node,e2e-linter,e2e-jest,e2e-a...
• nx affected --target=e2e --base=7418ae19c2b32f378a302508df688250017b641c --head=983eb555478caa3a0090a2217b544cf649145dc2 --exclude=e2e-storybook,e2e-react-native,e2e-detox --parallel=1
• nx affected --target=lint --base=7418ae19c2b32f378a302508df688250017b641c --head=983eb555478caa3a0090a2217b544cf649145dc2 --parallel=3
• nx affected --target=test --base=7418ae19c2b32f378a302508df688250017b641c --head=983eb555478caa3a0090a2217b544cf649145dc2 --parallel=1
• nx build typedoc-theme
• nx-cloud record -- yarn check-commit
• nx-cloud record -- yarn check-imports
• nx-cloud record -- yarn depcheck
• nx-cloud record -- yarn documentation
• nx-cloud record -- yarn nx format:check --base=7418ae19c2b32f378a302508df688250017b641c --head=983eb555478caa3a0090a2217b544cf649145dc2
• nx-cloud record -- yarn nx workspace-lint

---

Sent with 💌 from NxCloud.

[vercel]

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

1 Ignored Deployment

Name	Status	Preview	Updated
nx-dev	⬜️ Ignored (Inspect)		Jun 8, 2022 at 9:50PM (UTC)

[aqemi]

The root cause for this looks like located here
https://github.com/nrwl/nx/blob/master/packages/node/src/executors/node/node.impl.ts#L117

[AgentEnder]

@gioragutt can you rebase this? E2e failure looks unrelated

[gioragutt]

@gioragutt can you rebase this? E2e failure looks unrelated

Will do when I get back to my PC. Is it possible to just rerun the failed workflow?

[AgentEnder]

Yeah, the failure wasn't a timeout or similar that would indicate a flaky test though so I believe the rebase would be most beneficial

[gioragutt]

@AgentEnder CI passed 👍🏻

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