Update npm-run-all to the latest version 🚀

greenkeeper[bot] commented 7 years ago

Version 4.0.1 of npm-run-all just got published.

Dependency	npm-run-all
Current Version	3.1.2
Type	devDependency

The version 4.0.1 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.

Commits

The new version differs by 26 commits .

acb1582 4.0.1
378c54b Chore: switch to codecov
779720c Chore: fix trivial
6beda60 Docs: update README.md
558da4b Merge pull request #82 from vinkla/patch-1
181b689 Merge pull request #84 from bmarcaur/fix/npm-execpath-case-sensitivity
bb9e627 NPM_EXECPATH -> npm_execpath, this variable is case sensitive
81e3d0f Merge pull request #83 from evilebottnawi/patch-2
b40fc7e Fixed: typo in help CLI command.
0190327 Simplify repository config
750f5d9 Docs: fix README.md
5e88fb7 4.0.0
12b2b87 Breaking: use NPM_EXECPATH to run tasks
07bfec5 Chore: remove unused setting in .eslintrc.json
02e9767 New: --max-parallel option

There are 26 commits in total. 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:

coveralls commented 7 years ago

Coverage remained the same at 17.021% when pulling 1bcb02dc487d1a92470c7eb1b9b31b0c348b86f9 on greenkeeper/npm-run-all-4.0.1 into 35d227de68c257ed4e84db2721d779713aa60528 on master.

greenkeeper[bot] commented 7 years ago

Version 4.1.0 just got published.

Update to this version instead 🚀

Release Notes

v4.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 a task never finishes (e.g. web server, file watching, ...).
Thank you, @fatso83 !

Bug fixes

f7f7b43 fixed a bug that npm-run-all shows MaxListenersExceededWarning warnings if it runs many tasks in parallel.

Commits

The new version differs by 14 commits.

59219e8 4.1.0
f7f7b43 Fix: MaxListenersExceededWarning (fixes #105)
64f6479 Chore: use async/await in tests
66fa8ff Chore: upgrade dependencies
8c8bec0 Docs: update docs
8c6debf Chore: tweak CI settings
5fcc2c6 Chore: no package-lock
e07e782 New: add --aggregate-output option (fixes #36)(#104)
dff6409 Docs: add note about Yarn compatibility (#103)
94f1b64 Merge pull request #101 from ntwb/patch-1
a8364ce Add Node.j 8.x to AppVeyor CI
c6d3092 Add Node.js 8.x to Travis CI
873f036 Merge pull request #95 from goto-bus-stop/feature/docs-in-pkg
0fca0e0 Include docs in published npm package.

See the full diff

greenkeeper[bot] commented 7 years ago

Version 4.1.1 just got published.

Update to this version instead 🚀

Commits

The new version differs by 3 commits.

7e83545 4.1.1
ac9358a Chore: configure appveyor to run on only Node 8.
fbd4024 Fix: Use ansi-style directly instead of chalk.styles (#108)

See the full diff

greenkeeper[bot] commented 6 years ago

Version 4.1.2 just got published.

Update to this version instead 🚀

Release Notes

v4.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.
528d105...43a6b16 fixed the problem with using yarn (#113).