v4.1.5

🐛 Bug fixes

• 52eaf86...1b41ac5 switched ps-tree package to pidtree package for security reason.

v4.1.3

🐛 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

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

Bug fixes

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

v4.1.0

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

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

Bug fixes

• bb9e627 fixed the problem of npm_execpath on Mac/Linux (#84).
  Thank you, @bmarcaur !

v4.0.0

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

v3.1.2

Bug fixes

• 881c32f fixed that npm-run-all --version command had been broken. (#70)

Chore

• db8c7e9 removed the condition check about the entry file. (#67)

v3.1.1

Internal Changes

• e874a96 changed npm-run-all using npm run command instead of npm run-script command.