Skip to content

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 3, 2025

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package Change Age Confidence
npm-run-all ~3.1.2 -> ~4.1.0 age confidence

Release Notes

mysticatea/npm-run-all (npm-run-all)

v4.1.5

Compare Source

🐛 Bug fixes

v4.1.4

Compare Source

v4.1.3

Compare Source

🐛 Bug fixes

  • d56c268 improved label colors
  • 35f86ae fixed a bug that the script name which starts with ! makes npm-run-all confusing.

v4.1.2

Compare Source

Bug fixes

  • 096779b fixed the problem that --aggregate-output option does not work if child tasks print large output (#​111). Thank you, @​jlopezxs!
  • 693261b fixed the problem that --aggregate-output option does not work on npm-run-all command.
  • 528d105...43a6b16 fixed the problem with using yarn (#​113).

v4.1.1

Compare Source

Bug fixes

  • fbd4024 fixed a regression bug of --print-name.

v4.1.0

Compare Source

Features

  • e07e782 add --aggregate-output option. This option avoids that the output of tasks is mixed even if parallel mode. Don't use this option if a task never finishes (e.g. web server, file watching, ...).
    Thank you, @​fatso83 !

Bug fixes

  • f7f7b43 fixed a bug that npm-run-all shows MaxListenersExceededWarning warnings if it runs many tasks in parallel.

v4.0.2

Compare Source

Bug fixes

  • b90575b fixed unintentional failing of the assertion check about --race option. If there is a mix of --parallel and --serial then --race option had failed always. (fixes #​88).

v4.0.1

Compare Source

Bug fixes

v4.0.0

Compare Source

🎍 A happy new year! 🎍

Breaking changes

  • It dropped supports for Node 0.10, 0.12. See also: https://github.com/nodejs/LTS
  • It changed the way which finds the path of npm. Before, it was using npm command which is in environment variable PATH. Now, it uses the path of environment variable NPM_EXECPATH. If the NPM_EXECPATH is not defined, it uses the old way.
    The NPM_EXECPATH is set by npm in npm run-script command. This implies that npm-run-all uses npm which is running itself to run tasks.
    • It supports yarn. yarn run set the NPM_EXECPATH as similar to npm run-script.

Features

  • It added --max-parallel option. You can limit the number of parallelism by this option.
  • It added --npm-path option. You can specify the path of npm by this option. For example, npm-run-all foo --npm-path npm keeps the old behavior.
  • d7821df added colors for --print-label option. Thank you, @​nulltask !

Chore

  • It no longer uses babel to transpile.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/npm-run-all-4.x branch from dfae915 to 05cdc4a Compare August 11, 2025 08:07
@renovate renovate bot force-pushed the renovate/npm-run-all-4.x branch from 05cdc4a to 6a52751 Compare September 26, 2025 03:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants