v5.2.0

• Support limit of processes at once (#159, #175, #214)
• Allow different env vars for each command in the programmatic API (#184)

v5.1.0

• Return exit codes in the programmatic API (#213)

v5.0.2

• Update dependencies to get rid of vulnerability in tree-kill

v5.0.1

• Upgrade dependencies to get rid of vulnerability in os-locale (#204, #205)
• bin: remove duplicate entries from usage docs (#192)

v5.0.0

Breaking changes

• Timestamp formatting library date-fns was upgraded to v2.0.0 (#196)

Other changes

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

v4.1.2

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

v4.1.1

• bin: pass --prefix-length argument through (#189)

v4.1.0

• Add yarn support (#171 -- big thanks to @igrayson!)
• bin: fix concurrently --version
• docs: clarify API's successCondition option (#176)

v4.0.1

• Make success condition respect exiting order (as per docs), instead of command spec order

v4.0.0

More than anything, v4 is just a big refactor to allow changes to be made faster and more reliably.
It does feature some small breaking changes, and maybe even fixes some longstanding bugs.

Breaking changes

• The CLI option --allow-restarts is no more.
  Instead, just set --restart-tries to something greater than 0.
• Input handling is now opt-in via --handle-input flag. (#147)
  It does come with some specific input parsing that would make it difficult for you to use it with some tools.
• Setting prefix to none will now actually not prefix commands' outputs.
  Previously, it would prefix with [] .
• SIGINTs/Ctrl+C will now be handled gracefully. (#150)
  No more exiting with code 1 or tweaking --success flag.

No more null exit codes (#133)

That's a pretty bad bug that existed till now. You won't see a log like this anymore:

[1] npm run lint-watch exited with code null

What you will see going forward is the actual exit signal:

[1] npm run lint-watch exited with code SIGTERM

For Windows users, this will invariably still be exit code 1.

concurrently finally gets a shiny ✨ programmatic API!

Closes #101, #112. Maybe even #103.

const concurrently = require('concurrently');
await concurrently([
	'npm:watch-*',
	{ name: 'server', command: 'nodemon' }
], {
  prefix: 'name',
  killOthers: ['failure'],
  restartTries: 3
});

Check the docs here for some info on how to use it.