The version 4.1.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of npm-run-all.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notesv4.1.0
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 the task never finishes such as web server.
Thank you, @fatso83 !
Bug fixes
f7f7b43 fixed a bug that npm-run-all shows MaxListenersExceededWarning warnings if it runs many tasks in parallel.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
greenkeeper[bot]
commented
7 years ago
Version 4.1.0 of npm-run-all just got published.
The version 4.1.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of npm-run-all. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v4.1.0Features
--aggregate-outputoption. This option avoids that the output of tasks is mixed even if parallel mode. Don't use this option if the task never finishes such as web server.Thank you, @fatso83 !
Bug fixes
npm-run-allshowsMaxListenersExceededWarningwarnings if it runs many tasks in parallel.Commits
The new version differs by 14 commits.
59219e84.1.0f7f7b43Fix: MaxListenersExceededWarning (fixes #105)64f6479Chore: use async/await in tests66fa8ffChore: upgrade dependencies8c8bec0Docs: update docs8c6debfChore: tweak CI settings5fcc2c6Chore: no package-locke07e782New: add--aggregate-outputoption (fixes #36)(#104)dff6409Docs: add note about Yarn compatibility (#103)94f1b64Merge pull request #101 from ntwb/patch-1a8364ceAdd Node.j 8.x to AppVeyor CIc6d3092Add Node.js 8.x to Travis CI873f036Merge pull request #95 from goto-bus-stop/feature/docs-in-pkg0fca0e0Include docs in published npm package.See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: