--grep and --fgrep are now mutually exclusive; attempting to use both will cause Mocha to fail instead of simply ignoring --grep
--compilers is no longer supported; attempting to use will cause Mocha to fail with a link to more information
-d is no longer an alias for --debug; -d is currently ignored
#3275: --watch-extensions no longer implies js; it must be explicitly added (@TheDancingCode)
#2908: tap reporter emits error messages (@chrmod)
#2819: When conditionally skipping in a before hook, subsequent before hooks and tests in nested suites are now skipped (@bannmoore)
#627: Emit filepath in "timeout exceeded" exceptions where applicable (@boneskull)
#3556: lib/template.html has moved to lib/browser/template.html (@boneskull)
#2576: An exception is now thrown if Mocha fails to parse or find a mocha.opts at a user-specified path (@plroebuck)
#3458: Instantiating a Base-extending reporter without a Runner parameter will throw an exception (@craigtaub)
#3125: For consumers of Mocha's programmatic API, all exceptions thrown from Mocha now have a code property (and some will have additional metadata). Some Error messages have changed. Please use the code property to check Error types instead of the message property; these descriptions will be localized in the future. (@craigtaub)
📠 Deprecations
These are soft-deprecated, and will emit a warning upon use. Support will be removed in (likely) the next major version of Mocha:
-gc users should use --gc-global instead
Consumers of the function exported by bin/options should now use the loadMochaOpts or loadOptions (preferred) functions exported by the lib/cli/options module
Regarding the Mocha class constructor (from lib/mocha):
Use property color: false instead of useColors: false
Use property timeout: false instead of enableTimeouts: false
All of the above deprecations were introduced by #3556.
mocha.opts is now considered "legacy"; please prefer RC file or package.json over mocha.opts.
🎉 Enhancements
#3726: Add ability to unload files from require cache (@plroebuck)
Support all allowed node flags as supported by the running version of node (also thanks to @demurgos)
Support any V8 flag by prepending --v8- to the flag name
All flags are also supported via config files, package.json properties, or mocha.opts
Debug-related flags (e.g., --inspect) now imply--no-timeouts
Use of e.g., --debug will automatically invoke --inspect if supported by running version of node
Support negation of any Mocha-specific command-line flag by prepending --no- to the flag name
Interfaces now have descriptions when listed using --interfaces flag
Mocha constructor supports all options
--extension is now an alias for --watch-extensions and affects non-watch-mode test runs as well. For example, to run onlytest/*.coffee (not test/*.js), you can do mocha --require coffee-script/register --extensions coffee.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
@depfu rebase
Rebases against your default branch and redoes this update
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
Coverage remained the same at 80.769% when pulling a34d47be521fac83dde0d4b8ccda88d83f23a71f on depfu/update/npm/mocha-6.0.0 into eeaa4264dbdcc0be4ee086b4969ef630a15d2459 on master.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ mocha (^5.2.0 → ^6.0.0) · Repo · Changelog
Release Notes
6.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands