An in-range update of mocha is breaking the build 🚨

[greenkeeper]

Version 4.0.0 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.5.3
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha 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 failed Details

---

Release Notes

v4.0.0

4.0.0 / 2017-10-02

You might want to read this before filing a new bug! 😝

💥 Breaking Changes

For more info, please read this article.

Compatibility

• #3016: Drop support for unmaintained versions of Node.js (@boneskull):
  • 0.10.x
  • 0.11.x
  • 0.12.x
  • iojs (any)
  • 5.x.x
• #2979: Drop support for non-ES5-compliant browsers (@boneskull):
  • IE7
  • IE8
  • PhantomJS 1.x
• #2615: Drop Bower support; old versions (3.x, etc.) will remain available (@ScottFreeCode, @boneskull)

Default Behavior

• #2879: By default, Mocha will no longer force the process to exit once all tests complete. This means any test code (or code under test) which would normally prevent node from exiting will do so when run in Mocha. Supply the --exit flag to revert to pre-v4.0.0 behavior (@ScottFreeCode, @boneskull)

Reporter Output

• #2095: Remove stdout: prefix from browser reporter logs (@skeggse)
• #2295: Add separator in "unified diff" output (@olsonpm)
• #2686: Print failure message when --forbid-pending or --forbid-only is specified (@ScottFreeCode)
• #2814: Indent contexts for better readability when reporting failures (@charlierudolph)

👎 Deprecations

• #2493: The --compilers command-line option is now soft-deprecated and will emit a warning on STDERR. Read this for more info and workarounds (@ScottFreeCode, @boneskull)

🎉 Enhancements

• #2628: Allow override of default test suite name in XUnit reporter (@ngeor)

📖 Documentation

• #3020: Link to CLA in README.md and CONTRIBUTING.md (@skeggse)

🔩 Other

• #2890: Speed up build by (re-)consolidating SauceLabs tests (@boneskull)

Commits

The new version differs by 48 commits.

• d69bf14 Release v4.0.0
• 171b9f9 pfix "prepublishOnly" potential portability problem
• 60e39d9 Update link to wiki (GitHub at the leading --)
• 804f9d5 Update link because GitHub ate the leading --
• 3326c23 update CHANGELOG for v4.0.0 [ci skip]
• 6dd9252 add link to wiki on --compilers deprecation
• 96318e1 Deprecate --compilers
• 92beda9 drop bower support
• 58a4c6a remove unused .npmignore
• 7af6611 kill Date#toISOString shim
• 43501a2 reduce noise about slow tests; make a few tests faster, etc.
• fa228e9 update --exit / --no-exit integration test for new default behavior
• 3fdd3ff Switch default from forced exit to no-exit
• c5d69e0 add integration tests for --exit/--no-exit
• 3a7f8dc enhance runMochaJSON() helper by returning the subprocess instance

There are 48 commits in total.

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 🌴