The version 4.1.2 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of npm-run-all.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notesv4.1.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.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 4.1.2 of npm-run-all was just published.
The version 4.1.2 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of npm-run-all.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v4.1.2Bug fixes
--aggregate-outputoption does not work if child tasks print large output (#111). Thank you, @jlopezxs!--aggregate-outputoption does not work onnpm-run-allcommand.yarn(#113).Commits
The new version differs by 8 commits.
ec4d56c4.1.2cc8611cChore: upgrade dependencies43a6b16Chore: fix testsdfb9dcbFix: fix for latest yarn528d105Chore: trivial fix693261bFix: missing --aggregate-output in npm-run-all096779bFix:--aggregate-outputcannot handle large data (fixes #111)(#112)6ef64abChore: add Node 9 to Travis CISee the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: