Mach does not exit on Linux if esbuild errors are raised while not running in a TTY

[Benjozork]

Reproduction steps

import { execSync } from 'child_process';

// assuming mach.config.js lists instruments which fail to build

try {
    execSync('npx mach build', { stdio: 'inherit' }); // works, since it uses the tty from the node command
} catch (e) {
    // noop
}

try {
    execSync('npx mach build'); // stalls
} catch (e) {
    // noop
}

[Benjozork]

After further investigation this does not seem to happen on Windows.

[Benjozork]

After even more investigation, this seems to be a mixture of a node/docker image issue. It is possible something in Mach triggers this, as I cannot repro it with a simple script. But for now I will close this.