Skip to content

chore(deps): update dependency concurrently to v7 - autoclosed

Renovate requested to merge renovate/concurrently-7.x into master

This MR contains the following updates:

Package Type Update Change
concurrently devDependencies major 3.6.1 -> 7.5.0

Release Notes

open-cli-tools/concurrently

v7.5.0

Compare Source

What's Changed

Full Changelog: https://github.com/open-cli-tools/concurrently/compare/v7.4.0...v7.5.0

v7.4.0

Compare Source

New Contributors

v7.3.0

Compare Source

What's Changed

  • Export package.json path - #​339

v7.2.2

Compare Source

What's Changed

  • Update rxjs to version 7.0.0 - #​326
  • Fix TypeScript not able to resolve types when on Node 16 - #​330

New Contributors

v7.2.1

Compare Source

What's Changed

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

v7.2.0

Compare Source

New Contributors

v7.1.0

Compare Source

  • Excluding pattern support added, e.g. concurrently npm:lint:*(!fix) (#​305, #​306)
  • Fixed programmatic API docs to resemble v7.0.0 changes (#​303)

New Contributors

v7.0.0

Compare Source

🎉 🥂 Happy 2022!

Breaking 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.

Functional changes

  • Added --group flag/option to run process in parallel but print output in sequence - #​75, #​79, #​272
  • Codebase converted to TypeScript. Some bugs may arise due to this, but I hope not!

API Changes

  • concurrently can now be imported as an ES Module! Just do import concurrently from 'concurrently'.
  • concurrently() now returns the commands alongside a promise for the result - #​209

New Contributors

v6.5.1

Compare Source

v6.5.0

Compare Source

  • Add support for configuring via environment variables that start with CONCURRENTLY_ prefix (#​289)
  • Add --timings flag to show when each process started and stopped, and how long they ran for (#​291, #​295)

v6.4.0

Compare Source

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

v6.3.0

Compare Source

  • 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 (#​286)

v6.2.2

Compare Source

  • Remove read-pkg dependency which had a vulnerability issue (#​274)

v6.2.1

Compare Source

  • 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 (#​278)

v6.2.0

Compare Source

  • Include killed in the command result in programmatic API (#​250)
  • Make --restart-tries restart forever with negative values (#​263)

v6.1.0

Compare Source

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

v6.0.2

Compare Source

  • Fix --handle-input when input contains a colon (#​269)
  • Update lodash to fix a vulnerability (#​270, #​271)

v6.0.1

Compare Source

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

v6.0.0

Compare Source

v5.3.0

Compare Source

  • Added support for pnpm alongside npm and yarn (#​225)
  • Don't trim prefixes (#​231)
  • Included command info and index in the programmatic API (#​181, #​228)

v5.2.0

Compare Source

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

v5.1.0

Compare Source

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

v5.0.2

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source

Breaking changes

Other changes

v4.1.2

Compare Source

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.

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, or you tick the rebase/retry checkbox.

🔕 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 Renovate

Merge request reports