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.

Features

• 09507bcd326da38aa6e099e700fb5e659a4f17a7 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
  

Breaking Changes (and new features):

• 6d46ed9b5a4b6d3cfc28c67ec9d13cbbe0aeffef
  • If arguments are omitted, it came to remove argument placeholders (e.g., run-s "foo {1}" is evaluated to run-s "foo "). Until v2.3.0, the {1} is remained.
  • Argument placeholders came to support default values
    (e.g., run-s "start -- --port={1:=3000}"). This notation is similar to Shell Parameters. Currently, npm-run-all is supporting {parameter:-word} and {parameter:=word}.

Features:

• c24d1718eca354aab68b61f35da3be8a52c34ac4 --race option for a parallel execution. (#42)
  When a script finished even if the exit code is zero, npm-run-all kills other scripts. This is useful in order to run a test server and a test runner in parallel.

Upgrade Dependencies:

• shell-quote - https://nodesecurity.io/advisories/shell-quote_command-injection

Upgrade dependencies:

• minimatch - https://nodesecurity.io/advisories/minimatch_regular-expression-denial-of-service

Features:

• 97a1649ec6bfb73796f84ce6c0c7ab40479b894d Argument Placeholders feature was added (#44).
  Read more.
  Thank you @robario !

Upgrade:

• Upgraded cross-spawn package to 4.0.0.

Upgrade:

• Switched cross-spawn-async to cross-spawn (fixes #40).
  cross-spawn-async has been deprecated.

Features:

• Node API came to give results of child processes. See also: https://github.com/mysticatea/npm-run-all/blob/master/docs/node-api.md

  runAll(["clean", "lint", "build"])
      .then(results => {
          console.log(`${results[0].name}: ${results[0].code}`); // clean: 0
          console.log(`${results[1].name}: ${results[1].code}`); // lint: 0
          console.log(`${results[2].name}: ${results[2].code}`); // build: 0
      });
  

Features:

• New shorthand commands: run-s and run-p. Those are more simple commands than npm-run-all to cover most use cases.
  • run-s runs given npm-scripts sequencially. This is the shorthand of npm-run-all -s.
    e.g. run-s clean lint build:*
  • run-p runs given npm-scripts in parallel. This is the shorthand of npm-run-all -p.
    e.g. run-p "build:* -- --watch"

Breaking Changes:

• --continue-on-error option has been changed the behavior. On 1.x, if the option was specified, npm-run-all command exited with 0. But on 2.0.0, even if the option was specified, npm-run-all command will exit with a non-zero code if a npm-script exited with a non-zero code.
• --print-label, --print-name, and --continue-on-error options have been changed the behavior. On 1.x, the effect of those options was applied to only one script group. But on 2.0.0, the effect of those options will be applied to whole a command.
  For example, npm-run-all -s aaa bbb -p ccc ddd --print-label, in this case the command has 2 script group, aaa bbb and ccc ddd. Then, on 1.x, --print-label will effect to only ccc ddd. On the other hand, on 2.0.0, --print-label will effect to all of aaa, bbb, ccc, and ddd.
• -S and -P shorthand options have been removed. Please use originating options: -c and -c -p.

Features:

• 0a600e59d651283bcdc888b75e377488b47e427e - --print-name option has been added (#35).
  When this option was specified, npm-run-all prints task names before running the tasks.
  This option is useful with using --silent option or similar npm configulation.
• 00f674a6a516aa3ecbbc106a94ba9a3108385f1f - --print-label option has been added (#23).
  When this option was specified, npm-run-all prints task names as prefix for each line of output.
  This option is useful with using --parallel option. But there is a known limitation, some tools get stopping coloring when this option was specified.
  

New Features:

• 0a93527dc9838dbb00f944c3f9dba93c8b186233 --continue-on-error option was added (fixes #34). When this option was specified, npm-run-all continues subsequence on error.

  npm-run-all --sequential --continue-on-error foo bar    # shorthand: npm-run-all -S foo bar
  npm-run-all --parallel --continue-on-error foo bar      # shorthand: npm-run-all -P foo bar
  

New Features:

• 5f5d26faa1dfde744ec1a11f1ed1d2fcc6b14583 --serial option has been added as a synonym of --sequential option (#30)
  Thank you @sarbbottam!

Bug Fixes:

• c4a86daec725abfbe1e56571c244b629aff16a4a Added a workaround for Git Bash for Windows (#24, #25)

Bug Fixes:

• 413e45d087c0ca3a27342b77c3e636b253e8324b Improved Windows Supports (#26)
  Previously, npm-run-all has been failing if npm was installed to a path which includes space(s). Now this problem has fixed. Thanks @BarryThePenguin and cross-spawn-async!

Known Issues:

• On Git Bash for Windows, npm-run-all might hang up. (#24)
• A problem around parallel and nodemon has been reported. (#25)

I'm investigating those issues.

Bug Fixes:

• 36316eadb020e99c1ce7a86d8b5806f7efb8390c If the given tasks were not found, npm-run-all came to report an error (#19).

New Feature:

• 87aedbf187f2e554e9d6654c9475f4c93cd0ba91 --silent option was added. If this option was given, the log level of npm becomes silent (#18).

• npm-run-all came to transfer overwritten config values to nested calls (#13).

• Fix broken on Node.js v0.10.x (#17)

• Upgrade Babel 6
• Improve README.md
  • Add about the behavior of non-zero-exit.
  • Add about the arguments of tasks.

• Stopped using detach option to kill child processes with Process Group Id. Now, npm-run-all is using ps-tree then kills child processes.

• Added the support of overwritten configuration options (#13). You can use "--packageName:fieldName=value" options to overwrite package.json's config field.

  > npm-run-all build:* start --my-package:port=3000
  

• Improved the logic to kill child processes on UNIX-like platforms. Now npm-run-all kills child processes by using Process Group ID.

• I did refactoring npm-run-all's code.

• It comes to not skip duplication of tasks (#12).
• Tests for Node.js 5.x is added.

• Added a support for built-in tasks of npm.
  • restart
  • env

• Fixed a problem around using stdin in scripts.

What happened? q prefix!? I used npm version patch merely...

• Made CLI using inherit option for stdio of child processes (fixes #8).
• Updated dependencies.

• Now, when this runs tasks in parallel, if one of tasks exited with an error, this kills all tasks. So far the tasks are remained. (#6)
• Update dependencies.

• Update dependencies.
• Slim down npm-scripts.

• Fixed a help text (Thanks #4).
• Upgraded power-assert, Babel 5.x was supported.
• Added code coverage tracking.
• Added several tests.

• npm-run-all is using myself in its package.json.
  This had been turn off temporally to support Node 0.10.x.

• foo had run abc:foo task.
  This was a broken behavior.

• Add a support for Node v0.10.x
• New feature that glob-like matching notations.
• Update dependencies.

npm-run-all received the first PR. Thanks @k88hudson for your works!

npm-run-all --sequential clean lint --parallel watch:html watch:js mocha

--sequential/--parallel options make a group of tasks. --sequential option runs the tasks on sequential. --parallel option runs the tasks on parallel.

On whole, runs groups on sequential.

• Node API
  • options.stdin has documented, but had not implemented.
  • Add tests for stdio options.

CLI is not changed.

Use npm-run-all in my package.json.