Npm Run All Versions Save

🐛 Bug fixes

• 52eaf86242ba408dedd015f53ca7ca368f25a026...1b41ac569987c96e224f940ff59f9699322c7824 switched ps-tree package to pidtree package for security reason.

🐛 Bug fixes

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

Bug fixes

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

Bug fixes

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

Features

• e07e7821cce8c81f82c45c67ea25bcdeb9667094 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

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

Bug fixes

• b90575b0c9843d930680e27827fef49178a12d07 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).

Bug fixes

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

:bamboo: A happy new year! :bamboo:

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.
• d7821df56f264fcf291c26238e252667a1be623c added colors for --print-label option. Thank you, @nulltask !

Chore

• It no longer uses babel to transpile.

Bug fixes

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

Chore

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

Internal Changes

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