Contribution

• I'd be willing to implement this feature (contributing guide)

Describe the user story

We have multiple linters in our astro project (eslint, astro-check, svelte-check) and have structure like this:

"scripts": {
  "lint:eslint": "eslint .",
  "lint:svelte": "svelte-check",
  "lint:astro": "astro check"
}

We then use pnpm run /^lint:/ to run all linters in parallel. When one linter finds issues and stops with a non-zero exit code all other still running linters are killed. This means we don't get all lint issues in our CI for example and sometimes fix one found issue to find another one by a different linter when running all lints again.

Describe the solution you'd like

An option similar to the proposed #6792 but kind of opposite: wait until all scripts have stopped running and then return with the exit code of the first failed script.

npm-run-all calls this option --continue-on-error. Another option might be --wait-for-all

Describe the drawbacks of your solution

One drawback: we lose the specific exit codes of the scripts that failed after the first one.

Also the additional logic of wether to stop the execution might add non-trivial complexity.

Describe alternatives you've considered

I've considered writing a small script or use npm-run-all. The latter hasn't been updated and I would like to avoid the additional dependency, because I really like that we can new lint:XXX scripts and they will be run in our CI.