[bug] Hide Windows consoles spawned by Nx task execution

[the-ult]

01: Hide Windows consoles spawned by Nx task execution

Problem

When a multi-project Nx command runs on Windows, Nx can open many visible node.exe console windows. The number of windows follows the number of forked task processes. This is especially disruptive during affected and run-many commands.

The issue was observed with Nx 23.2.1, Node.js 22 or newer, and a forked task executor. The individual task can still finish successfully. The unwanted windows are a process-management problem in Nx, not a lint or test failure.

Reproduction

1. Use Windows with Nx 23.2.1.
2. Run a multi-project command such as nx affected -t test --parallel=4 --configuration=ci.
3. Observe the visible Node console windows while Nx runs the tasks.

The workspace currently uses a local package patch as a workaround. The unpatched Nx release still creates the windows.

Expected behavior

Nx should hide every Windows console created for a forked task process. Nx should still stream task output, pass messages over IPC, report task status, and clean up child processes as it does today.

Proposed fix

What to build: Nx task execution on Windows must run forked task processes without opening a visible console window for each task. Lint, test, and generation tasks must keep their current output, IPC, exit codes, and parallel behavior.

Pass Node's windowsHide: true option to every forked child process used by the Nx task runner. Cover the batch worker, normal executor worker, direct-output worker, and pseudo-terminal bridge.

Add regression coverage at the task-runner process-creation seam. The test should verify that each fork path requests hidden Windows consoles and that the existing task lifecycle still works.

Acceptance criteria

• Running a multi-project Nx command on Windows does not open visible Node console windows for forked task processes.
• Batch, normal executor, direct-output, and pseudo-terminal task paths all use hidden Windows child processes.
• Task output, IPC, exit codes, cancellation, and cleanup remain unchanged.
• Non-Windows task execution remains unchanged.
• The upstream TypeScript build accepts the child-process option, or uses an equivalent typed approach without weakening the task-runner contract.
• Regression coverage protects the hidden-window behavior.

References

• Nx 23.2.1 release: https://github.com/nrwl/nx/releases/tag/23.2.1
• Nx task runner source: https://github.com/nrwl/nx/blob/23.2.1/packages/nx/src/tasks-runner/forked-process-task-runner.ts
• Nx pseudo-terminal bridge: https://github.com/nrwl/nx/blob/23.2.1/packages/nx/src/tasks-runner/fork.ts
• Node.js child_process API: https://nodejs.org/api/child_process.html#child_processforkmodulepath-args-options
• Node.js spawn() options: https://nodejs.org/api/child_process.html#child_processspawncommand-args-options