PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

When running nest start, pressing Ctrl+C (SIGINT) causes the parent CLI process to immediately kill the child NestJS application via treeKillSync, without giving it time to execute async shutdown hooks (onModuleDestroy, onApplicationShutdown). This means graceful shutdown logic (closing DB connections, flushing logs, etc.) never runs.

Issue Number: #3158

What is the new behavior?

The parent process now installs SIGINT and SIGTERM handlers that forward the signal to the child process via childProcessRef.kill(signal) instead of killing it immediately. The parent stays alive until the child exits naturally, giving the NestJS application time to run its async shutdown lifecycle hooks before the process terminates.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

Files changed:

• actions/start.action.ts — Added signal forwarding handlers that send SIGINT/SIGTERM to the child process instead of killing it immediately
• test/actions/start.action.spec.ts — Added 4 regression tests verifying signal forwarding behavior