-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of npm-run-all is breaking the build 🚨 #105
Comments
After pinning to 4.0.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 4.1.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.1.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.1.2Bug fixesCommitsThe new version differs by 8 commits.
See the full diff |
Version 4.1.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 6 commits.
See the full diff |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
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-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
npm-run-all
showsMaxListenersExceededWarning
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 🌴
The text was updated successfully, but these errors were encountered: