Releases: mysticatea/npm-run-all
Releases · mysticatea/npm-run-all
v4.1.5
🐛 Bug fixes
- 52eaf86...1b41ac5 switched
ps-treepackage topidtreepackage for security reason.
v4.1.3
v4.1.2
v4.1.1
v4.1.0
Features
- e07e782 add
--aggregate-outputoption. 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-allshowsMaxListenersExceededWarningwarnings if it runs many tasks in parallel.
v4.0.2
v4.0.1
v4.0.0
🎍 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 usingnpmcommand which is in environment variablePATH. Now, it uses the path of environment variableNPM_EXECPATH. If theNPM_EXECPATHis not defined, it uses the old way.
TheNPM_EXECPATHis set by npm innpm run-scriptcommand. This implies thatnpm-run-allusesnpmwhich is running itself to run tasks.- It supports
yarn.yarn runset theNPM_EXECPATHas similar tonpm run-script.
- It supports
Features
- It added
--max-paralleloption. You can limit the number of parallelism by this option. - It added
--npm-pathoption. You can specify the path ofnpmby this option. For example,npm-run-all foo --npm-path npmkeeps the old behavior. - d7821df added colors for
--print-labeloption. Thank you, @nulltask !
Chore
- It no longer uses babel to transpile.