CI Pipeline does not receive proper exit codes

[AndyOGo]

First I wanna state that this is a great library.
Though I face the issue that if one of my build scripts breaks my CI is not "notified" though proper erring exit codes, instead my npm scripts just hangs and does nothing.
I expect that if my JS or CSS or anything breaks, that all other scripts can be cancelled and that the parent process exits which non-zero code.
May I miss some CLI option?

I use npm-run-all v^4.0.1 in combination with better-npm-run v0.0.11

[AndyOGo]

I just tried same setup with cross-env, unfortunately with same results 😞

[AndyOGo]

I further investigated this issue and surprisingly found that it does not seem to be an issue with npm-run-all at all.

Turned out that:

• node-sass in combination with node-sass-import-once as the importer, does neither throw nor setting process.exitCode properly in case of an imported module can't be found - see: Does not stop CI build if Could not import error at-import/node-sass-import-once#35
• even though I use webpack's bail option it does exit with code 0
  related: bail option does not exit the process codymikol/karma-webpack#66
  Webpack client does not throw error code when build failed webpack/webpack#708
  Webpack process doesn't exit (not in watch mode) webpack/webpack#3170
• HappyPack hangs CI build does not bail with proper exit code amireh/happypack#133

To double check that npm-run-all does things right, wrote some small test scripts which throw at various posistions, namely first-line, within setImmediate callback and within setTimeout callback. All of them worked perfectly...

[AndyOGo]

@mysticatea
Sorry for my wrong bug report.
I could solve all issues by fixing/workaround above issues ... will close.