Update npm-run-all to the latest version 🚀 #1462
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
xPaw
approved these changes
Aug 26, 2017
greenkeeper
bot
added
the
Type: Dependencies
astorije
approved these changes
Aug 26, 2017
matburnham
pushed a commit
to matburnham/lounge
that referenced
this pull request
Sep 6, 2017
…all-4.1.0 Update npm-run-all to the latest version 🚀
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 and of course you may always ask my humans.
Your Greenkeeper Bot 🌴