Version 4.1.0 of npm-run-all just got published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
npm-run-all
|
|
Current Version
|
4.0.2
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
As npm-run-all is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
- ❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
- ❌ continuous-integration/appveyor/branch AppVeyor build failed Details
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 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.
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
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 🌴
Version 4.1.0 of npm-run-all just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As npm-run-all is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
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 a 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 🌴