concurrently

Dropped support for Node.js <22.0.0. Older Node.js version have reached end-of-life, and certain features require new-ish JS APIs.

Concurrently is now ESM-only. It's now possible to require(esm). See here for interoperability.

Prefix colors now default to automatic - #581 The colors used to default to reset (which does nothing). Concurrently now automatically selects a color, out of the box. The list of colors used is not jarring nor carries semantic meaning, and reads well in both dark and light terminal backgrounds.

Removed deprecated flags and options

Dropped support for Node.js < 18.0.0. Older Node.js version have reached end-of-life, and certain features require new-ish JS APIs.

Pending commands no longer run when --max-processes is set and an interruption/kill signal is sent - #433, #452, #460 Before v9.0.0, pressing Ctrl+C when --max-processes is set meant that only those commands would receive it. Once these stopped, the pending commands would start, which in turn meant that another Ctrl+C press would be necessary to stop them, and so on. Similar situation applied to combining --max-processes with --kill-others/--kill-others-on-fail.

The concurrently and default exports are now the same - #399 It's reasonable to expect that import { concurrently } from 'concurrently' would work the same as import concurrently from 'concurrently', however this has not been the case. The former used to be an unconfigured version of concurrently, lacking all features that you'd get from the CLI, which was seen as a "footgun". Both are now the same function.

Drop support for Node.js v12 & add support for Node.js v18

Dropped support for Node 10. Minimum version is now 12.20.

concurrently() API now has a different return value. Please refer to the docs.