fix(misc): @nx/web:file-server should not error on destructuring null

[AgentEnder]

Current Behavior

The daemon watcher sometimes returns an error, and when doing so the second arg is null. This results in an error:

TypeError: Cannot destructure property 'changedFiles' of 'object null' as it is null.
    at /Users/dnichols2/Documents/Repos/webplatform.ui/node_modules/@nx/web/src/executors/file-server/file-server.impl.js:81:24
    at Socket.<anonymous> (/Users/dnichols2/Documents/Repos/webplatform.ui/node_modules/nx/src/daemon/client/client.js:121:17)
    at Socket.emit (node:events:517:28)
    at Pipe.<anonymous> (node:net:350:12)

Expected Behavior

There is not an error on the restructuring logic, preserving the original error message.

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	Nov 17, 2023 5:39pm

[nx-cloud]

☁️ Nx Cloud Report

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

---

Sent with 💌 from NxCloud.

[ndcunningham]

LGTM

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