Update npm-run-all to the latest version 🚀 #42
Closed
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}
Version 4.1.3 just got published.Update to this version instead 🚀 CommitsThe new version differs by 6 commits.
See the full diff |
|
|
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.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 11 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 CI7e835454.1.1ac9358aChore: configure appveyor to run on only Node 8.fbd4024Fix: Use ansi-style directly instead of chalk.styles (#108)See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴