Skip to content

Releases: mysticatea/npm-run-all

v4.1.5

24 Nov 14:04
v4.1.5
df15118
Compare
Choose a tag to compare

🐛 Bug fixes

v4.1.3

24 Nov 14:02
52eaf86
Compare
Choose a tag to compare

🐛 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

07 Nov 11:55
v4.1.2
ec4d56c
Compare
Choose a tag to compare

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

28 Aug 09:34
v4.1.1
7e83545
Compare
Choose a tag to compare

Bug fixes

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

v4.1.0

26 Aug 14:10
v4.1.0
59219e8
Compare
Choose a tag to compare

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

22 Feb 22:28
v4.0.2
46cfd57
Compare
Choose a tag to compare

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

17 Jan 11:15
v4.0.1
acb1582
Compare
Choose a tag to compare

Bug fixes

v4.0.0

31 Dec 16:03
5e88fb7
Compare
Choose a tag to compare

🎍 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

01 Dec 03:39
v3.1.2
2ec9889
Compare
Choose a tag to compare

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

15 Oct 10:37
v3.1.1
3038a53
Compare
Choose a tag to compare

Internal Changes

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