fix(nextjs): Surface error codes when build is interrupted by signals SIGINT, SIGTERM etc...

[ndcunningham]

When the nx/next:build executor is abruptly interrupted due to a signal such as SIGKILL we should surface these signals downstream so that they can be outputted to the console.

fixes: #22148

[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)		Mar 6, 2024 10:49pm

[nx-cloud]

☁️ Nx Cloud Report

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

---

Sent with 💌 from NxCloud.

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