concurrently
10.0.6 · 8 Oct 2026MIT29.2M / weekRepositoryHomepagenpmAtom feed
72 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 4.x
4.0.1
26 Aug 2018Make success condition respect exiting order (as per docs), instead of command spec order
4.0.0
24 Aug 2018- breaking
The CLI option
--allow-restartsis no more.
Instead, just set--restart-triesto something greater than0. - breaking
Input handling is now opt-in via
--handle-inputflag.
It does come with some specific input parsing that would make it difficult for you to use it with some tools. - breaking
Setting prefix to
nonewill now actually not prefix commands' outputs.
Previously, it would prefix with.
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
- breaking
The CLI option
--allow-restartsis no more.
Instead, just set--restart-triesto something greater than0. - breaking
Input handling is now opt-in via
--handle-inputflag.
It does come with some specific input parsing that would make it difficult for you to use it with some tools. - breaking
Setting prefix to
nonewill now actually not prefix commands' outputs.
Previously, it would prefix with. - breaking
SIGINTs/Ctrl+C will now be handled gracefully.
No more exiting with code1or tweaking--successflag.
No more
nullexit 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.
- 3.x
3.6.1
24 Jul 2018Fix inability to change the prefix to a template like
{time}-{pid}
3.6.0
19 Jun 2018Expand
npm:prefix tonpm runSupport wildcard expansion for
npm:something-*/npm:*-like commands
3.2.0
8 Feb 2017Upgrade spawn-default-shell dependency to v2.0.0. This means that shells in Linux and Mac will spawn with the
--loginflag, allowing you to make use of/etc/profile,~/.profile, and etc
Add support for colors in subprocesses when they use chalk (#49, #86, #87)
Upgrade spawn-default-shell dependency to v2.0.0. This means that shells in Linux and Mac will spawn with the
--loginflag, allowing you to make use of/etc/profile,~/.profile, and etcThe timestamps are now handled by date-fns instead of Moment.js. They share the same date format patterns.
Also, this version drops support for Node 0.12. We're only supporting Node 4+.
3.1.0
2 Oct 2016Bumps spawn-default-shell to 1.1.0: github.com/kimmobrunfeldt/spawn-default-shell/r…
3.0.0
26 Sep 2016Fix issues with Windows and Appveyor CI was added to ensure Windows compability
Improve shell support. spawn-default-shell is used to spawn shell commands. It uses the best available shell on your platform. You can also customize the used shell with SHELL and SHELL_EXECUTION_FLAG environment variables. Minor caveat: it means that e.g. piping works on your linux machine but may not work as expected on Windows. This leaves more responsibility to the users of concurrently.
Handle SIGTERM and SIGINT signals correctly
This release includes huge amount of improvements. Major updates:
Fix issues with Windows and Appveyor CI was added to ensure Windows compability
Improve shell support. spawn-default-shell is used to spawn shell commands. It uses the best available shell on your platform. You can also customize the used shell with SHELL and SHELL_EXECUTION_FLAG environment variables. Minor caveat: it means that e.g. piping works on your linux machine but may not work as expected on Windows. This leaves more responsibility to the users of concurrently.
Handle SIGTERM and SIGINT signals correctly
Closes these PRs: #58 #57 #56 #53 #47 #45 #43 #42 #40 #21. Closes these issues: #52 #50 #41 #31 #28 #7 #3.
- 2.x
2.0.0
16 Feb 2016- 1.x
1.0.0
15 Nov 2015Thanks, @paulerickson
Thanks, @msikma
Added these features:
Thanks, @paulerickson
Thanks, @msikma
- 0.1.x
0.1.1
27 May 2015Fix a few small output formatting bugs.
Add tests
0.1.0
25 May 2015No breaking changes
- 0.0.x
0.0.5
8 Feb 2015Remove forgotten console.log
0.0.4
8 Feb 2015Add new prefix: index
Use index as prefix by default
Make process prefix dimmed gray to prevent distracting
Add new prefix: index
Use index as prefix by default
Make process prefix dimmed gray to prevent distracting
Add --raw option
Add --prefix-length option
Improve --help
Refactor code organization
Change prefix command to show also stuff at end of the command too