Update dependency concurrently to v9 #13
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
8.2.2
->9.1.0
Release Notes
open-cli-tools/concurrently (concurrently)
v9.1.0
Compare Source
What's Changed
New Contributors
Full Changelog: open-cli-tools/concurrently@v9.0.1...v9.1.0
v9.0.1
Compare Source
What's Changed
Full Changelog: open-cli-tools/concurrently@v9.0.0...v9.0.1
v9.0.0
Compare Source
💥 Breaking Changes
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, #460Before 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 - #399It's reasonable to expect that
import { concurrently } from 'concurrently'
would work the same asimport 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.✨ New Features
Use
--restart-after exponential
. Restarts happen at2^N
seconds.--pad-prefix
flag - #166, #417, #495--teardown
flag - #472, #500node:<script>
commands tonode --run <script>
- #475state
field toCommand
- #455🐛 Bug Fixes
spawn-command
when running in Node 22 - #407, #477, #479, #492--raw
and--hide
compatible - #394, #486Other Changes
--help
no longer shows examples due to there being too many.Refer to https://github.com/open-cli-tools/concurrently/tree/v9.0.0/docs instead, or to the
node_modules/concurrently/docs
directory in your project.--passthrough-arguments
- #490date-fns
with hand-rolled date formatting - #436, #443This should make installing concurrently faster.
New Contributors
Full Changelog: open-cli-tools/concurrently@v8.2.2...v9.0.0
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.