v3.1.0

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

v3.0.0

Breaking Changes (and new features):

• 6d46ed9
  • 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}.

v2.3.0

Features:

• c24d171 --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.

v2.2.2

Upgrade Dependencies:

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

v2.2.1

Upgrade dependencies:

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

v2.2.0

Features:

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

v2.1.2

Upgrade:

• Upgraded cross-spawn package to 4.0.0.

v2.1.1

Upgrade:

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

v2.1.0

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
      });

v2.0.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.