concurrently

Skip force-kill logging when no processes remain

Correctly output non-ASCII text on Windows

Expand wildcards from package.json5 when package.json is missing

Avoid kill timeout exit delays

Ensure FlowController type is exported - #594

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.

Upgrade shell-quote to 1.9.0 - #597, #600

Address vulnerability in shell-quote - #591, #596

Remove lodash

Replace jest with vitest

Upgrade to pnpm v10

Don't throw when there are no commands

Add --kill-timeout

Handle SIGPIPEs

Add ability to have custom logger

Support Deno's JSON with comments configuration

Remove signal event listeners on finish

Add support for Deno shortcuts and wildcards

bin: Show help when no args are passed

Don't set up more than 1 abort signal listener

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.

Starting with v9.0.0, this no longer happens, as these flags and/or key presses send a signal to stop the running commands in addition to preventing new commands from running.

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.

If you'd like to access the unconfigured function, use import { createConcurrently } from 'concurrently' instead.

suggestion: prefixColors API type to embrace string type

Test against Node.js v20 instead of v19

Delay summary timings output until finished

Replace deprecated RxJS code

Support REPL languages that use colons

Move types condition to the front

Allow setting raw per command when using the API

Fix release workflow

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

Add support for Bun

Add --kill-signal option

Support percent values in maxProcesses

Enable TypeScript strict mode

Update install command to use --save-dev

Add auto colors functionality

Fix onFinish signature when using exactOptionalPropertyTypes

Add shorthand conc - #358

Export package.json path - #339

Update rxjs to version 7.0.0 - #326

Fix TypeScript not able to resolve types when on Node 16 - #330

Fix --success command- syntax when command name has dashes - #324, #325

Support passthrough of additional arguments to commands via placeholders - #33, #282, #307

Add command-{name|index} and !command-{name|index} to --success - #280, #281, #318

Excluding pattern support added, e.g. concurrently npm:lint:*(!fix) (#305, #306)

Fixed programmatic API docs to resemble v7.0.0 changes

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

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

Added --group flag/option to run process in parallel but print output in sequence - #75, #79, #272

Fix command names when using npm wildcard (#148, #165, #211, #212)

Add support for configuring via environment variables that start with CONCURRENTLY_ prefix

Add --timings flag to show when each process started and stopped, and how long they ran for (#291, #295)

Add --hide flag to hide the output of specified commands (#138, #173)

Distribute prefix colors correctly when using npm/yarn/pnpm script expansion (#186, #210, #234, #286)

Add new option to programmatic API, prefixColors, which serves as fallback for commands without a prefixColor

Remove read-pkg dependency which had a vulnerability issue

Fix hanging issue after using programmatic API to read from stdin (#252, #253)
Big kudos to @brandonchinn178 for finding and fixing this! 🏆 🎉

Correctly reexport flow controllers

Include killed in the command result in programmatic API

Make --restart-tries restart forever with negative values

Change default color to reset (no color set), instead of gray.dim (#259, #275)

Update lodash to fix a vulnerability (#270, #271)

Fix --handle-input when input contains a colon

Fix cwd option not overwriting per command if specified in programmatic API (#266, #268)

Dropped support for Node 8

prefixColors option now accepts HEX colors (#260, #261)

Added cwd option to programmatic API (#216, #246)

Added support for pnpm alongside npm and yarn

Don't trim prefixes

Included command info and index in the programmatic API (#181, #228)

Support limit of processes at once (#159, #175, #214)

Allow different env vars for each command in the programmatic API

Return exit codes in the programmatic API

Upgrade dependencies to get rid of vulnerability in os-locale (#204, #205)

bin: Remove duplicate entries from usage docs

Timestamp formatting library date-fns was upgraded to v2.0.0

Kill child processes on SIGHUP (#193, #195)

Don't strip quotes if they are impaired (#118, #194)

bin: Pass --prefix-length argument through