Skip to content

Update dependency concurrently to v4

Gitter Badger requested to merge renovate/concurrently-4.x into develop

This MR contains the following updates:

Package Type Update Change References
concurrently devDependencies major ^2.0.0 -> ^4.0.0 source

Release Notes

kimmobrunfeldt/concurrently

v4.1.1

Compare Source

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

v4.1.0

Compare Source

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

v4.0.1

Compare Source

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

v4.0.0

Compare Source

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.

v3.6.1

Compare Source

  • Fix inability to change the prefix to a template like {time}-{pid} (#​152)

v3.6.0

Compare Source

  • Expand npm: prefix to npm run (#​126)
  • Support wildcard expansion for npm:something-*/npm:*-like commands (#​140)
  • Handle stdin (#​121, #​128)
  • Upgrade own chalk version (#​146)

BIG thanks to @​pgraham for contributing with the most important changes of this version!

v3.5.1

Compare Source

v3.5.0

Compare Source

  • Add flags for restarting processes: --allow-restart, --restart-after, --restart-tries (#​48, #​100)
  • Default --prefix to name when --names is set (#​97)

v3.4.0

Compare Source

  • Don't try to kill other processes while they are already being killed (#​92, #​91)
  • Add new --kill-others-on-fail flag (#​93, #​64, #​55)
  • Remove kill delay
    This feature would cause more problems than it would help as per comments on #​92. Could perhaps be added back in the future.

v3.3.0

Compare Source

Switch spawn-default-shell with spawn-command due to lots of problems in v3.2.0.

v3.2.0

Compare Source

  • Add support for colors in subprocesses when they use chalk (#​49, #​86, #​87)
  • Fix killing processes in Windows gitbash (#​74, #​67)
  • Upgrade spawn-default-shell dependency to v2.0.0. This means that shells in Linux and Mac will spawn with the --login flag, allowing you to make use of /etc/profile, ~/.profile, and etc (#​81)
  • The timestamps are now handled by date-fns instead of Moment.js. They share the same date format patterns. (#​77)

Also, this version drops support for Node 0.12. We're only supporting Node 4+.

v3.1.0

Compare Source

Bumps spawn-default-shell to 1.1.0: https://github.com/kimmobrunfeldt/spawn-default-shell/releases/tag/1.1.0

v3.0.0

Compare Source

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 MRs: #​58 #​57 #​56 #​53 #​47 #​45 #​43 #​42 #​40 #​21. Closes these issues: #​52 #​50 #​41 #​31 #​28 #​7 #​3.

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever MR becomes conflicted.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

  • If you want to rebase/retry this MR, check this box

This MR has been generated by Renovate Bot.

Edited by Eric Eastwood

Merge request reports