fix(js): node executor handles processes robustly

[Coly010]

Current Behavior

The @nx/js:node executor had several process management issues:

• Multiple concurrent builds could cause overlapping/corrupted console output,
  especially in NestJS projects
• Process stdout streams weren't properly coordinated between different tasks
• Rapid file changes could trigger multiple simultaneous rebuilds without
  proper debouncing
• Console output formatting could break with mixed output from overlapping
  processes

Expected Behavior

The node executor should:

• Handle process output streams cleanly with no overlapping/corrupted output
• Properly debounce rebuild triggers to prevent resource conflicts
• Maintain clean console formatting even with rapid file changes
• Coordinate output between concurrent processes using a global stream manager

Related Issue(s)

Fixes #30247
Fixes #22999
Fixes #22945

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
nx-dev	Ready	Preview	Aug 15, 2025 5:25pm

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 42b416d

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e,e2e-c...	✅ Succeeded	39m 36s	View ↗
nx run-many -t check-imports check-commit check...	✅ Succeeded	1m 46s	View ↗
nx-cloud record -- nx-cloud conformance:check	✅ Succeeded	2s	View ↗
nx-cloud record -- nx format:check	✅ Succeeded	6s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	5s	View ↗
nx documentation	✅ Succeeded	1m 51s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-08-15 17:58:11 UTC

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