Update mocha to the latest version 🚀 #638
Merged
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}
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 5.0.0 of mocha was just published.
The version 5.0.0 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 mocha.
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
v5.0.05.0.0 / 2018-01-17
Mocha starts off 2018 right by again dropping support for unmaintained rubbish.
Welcome @vkarpov15 to the team!
💥 Breaking Changes
Practically speaking, only code which consumes (through bundling or otherwise) the userland buffer module should be affected. However, Mocha will no longer test against these browsers, nor apply fixes for them.
🎉 Enhancements
--filecommand line argument (documentation) (@hswolff)🐛 Fixes
😎 Developer Experience
📖 Documentation
--no-timeoutsdocs (@dfberry)done()callback docs (@maraisr)README.mdorganization (@xxczaki)🔩 Other
Commits
The new version differs by 26 commits.
cc4a818Release v5.0.09f61c04finalize v5.0.0 CHANGELOG [ci skip]a7267b4remove more references to make and Makefiledc58252prep changelog for v5.0.0 [ci skip]f8a1d2adocs(index): add missing doc link (#3203); closes #3135401997fupdate package-lock.json50aec7aAdd ability to pass in test files to be ran before positional files via --file (#3190)7d8abe0fix id and class definition0a3e32bRewrite Makefile using NPS Scripts. Closes #2352c7730a6Drop TextMate integration inside mocha closes #31185c6e99bupdate ESM tests to run against headless chrome instead of saucelabs' chrome onlyac1dd70attempt to get travis working againe8b5592Align netlify config with admin panel565726dAdded Netlify config filee54370ereplace phantomjs with puppeteer for browser tests; closes #3128There are 26 commits in total.
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 🌴