May 6, 2018

@mysticatea mysticatea released this Nov 7, 2017 · 6 commits to master since this release

Assets 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).

@mysticatea mysticatea released this Aug 28, 2017 · 14 commits to master since this release

Assets 2

Bug fixes

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

@mysticatea mysticatea released this Aug 26, 2017 · 17 commits to master since this release

Assets 2

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.

@mysticatea mysticatea released this Feb 22, 2017 · 31 commits to master since this release

Assets 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).

@mysticatea mysticatea released this Jan 17, 2017 · 33 commits to master since this release

Assets 2

Bug fixes

@mysticatea mysticatea released this Dec 31, 2016 · 44 commits to master since this release

Assets 2

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

@mysticatea mysticatea released this Dec 1, 2016 · 59 commits to master since this release

Assets 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)

@mysticatea mysticatea released this Oct 15, 2016 · 65 commits to master since this release

Assets 2

Internal Changes

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

@mysticatea mysticatea released this Sep 1, 2016 · 70 commits to master since this release

Assets 2

Features

  • 09507bc added supporting $npm_config_xxx (fixes #60)

    npm run-script command has supported --name=value style options. This style options make environment variables $npm_config_name (%npm_config_name% on Windows), then we can use those environment variables in npm-scripts. Now npm-run-all also got supports of the --name=value style options and $npm_config_name variables.
    For examples:

    {
        "scripts": {
            "echo": "echo $npm_config_foo"
        }
    }
    $ npm run echo --foo=777
    777
    $ npm-run-all echo --foo=888
    888