This repository was archived by the owner on Jun 22, 2021. It is now read-only.
chore(deps): update dependency mocha to v9 #526
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.
This PR contains the following updates:
5.2.0->9.0.0Release Notes
mochajs/mocha
v9.0.0Compare Source
💥 Breaking Changes
#4633: Drop Node.js v10.x support (@juergba)
#4635:
import-first loading of test files (@giltayar)Mocha is going ESM-first! This means that it will now use ESM
import(test_file)to load the test files, instead of the CommonJSrequire(test_file). This is not a problem, asimportcan also load most files thatrequiredoes. In the rare cases where this fails, it will fallback torequire(...). This ESM-first approach is the next step in Mocha's ESM migration, and allows ESM loaders to load and transform the test file.#4636: Remove deprecated
utils.lookupFiles()(@juergba)#4638: Limit the size of
actual/expectedfordiffgeneration (@juergba)#4389: Refactoring: Consuming log-symbols alternate to code for win32 in reporters/base (@MoonSupport)
🎉 Enhancements
--dry-run(@juergba)🐛 Fixes
🔩 Other
Runner(suite: Suite, delay: boolean)signature (@juergba)v8.4.0Compare Source
🎉 Enhancements
🐛 Fixes
📖 Documentation
options.requireto Mocha constructor forroot hookplugins on parallel runs (@juergba)top-level awaitand ESM test files (@juergba)Also thanks to @outsideris for various improvements on our GH actions workflows.
v8.3.2Compare Source
🐛 Fixes
requireinterface (@alexander-fenster)📖 Documentation
v8.3.1Compare Source
🐛 Fixes
EvalErrorcaused by regenerator-runtime (@snoack)importfrom mocha in parallel mode (@nicojs)v8.3.0Compare Source
🎉 Enhancements
🐛 Fixes
requireerror when bundling Mocha with Webpack (@devhazem)📖 Documentation
🔩 Other
Also thanks to @outsideris and @HyunSangHan for various fixes to our website and documentation.
v8.2.1Compare Source
Fixed stuff.
🐛 Fixes
Promiserejections and erroneous "done()called twice" errors (@boneskull)MaxListenersExceededWarningin watch mode (@boneskull)Also thanks to @akeating for a documentation fix!
v8.2.0Compare Source
The major feature added in v8.2.0 is addition of support for global fixtures.
While Mocha has always had the ability to run setup and teardown via a hook (e.g., a
before()at the top level of a test file) when running tests in serial, Mocha v8.0.0 added support for parallel runs. Parallel runs are incompatible with this strategy; e.g., a top-levelbefore()would only run for the file in which it was defined.With global fixtures, Mocha can now perform user-defined setup and teardown regardless of mode, and these fixtures are guaranteed to run once and only once. This holds for parallel mode, serial mode, and even "watch" mode (the teardown will run once you hit Ctrl-C, just before Mocha finally exits). Tasks such as starting and stopping servers are well-suited to global fixtures, but not sharing resources--global fixtures do not share context with your test files (but they do share context with each other).
Here's a short example of usage:
Fixtures are loaded with
--require, e.g.,mocha --require fixtures.js.For detailed information, please see the documentation and this handy-dandy flowchart to help understand the differences between hooks, root hook plugins, and global fixtures (and when you should use each).
🎉 Enhancements
test.js) now usable with--extensionoption (@jordanstephens).js,.test.js) now usable with--extensionoption (@boneskull)jsonreporter now containsspeed("fast"/"medium"/"slow") property (@wwhurin)For implementors of custom reporters:
Runner.prototype.workerReporter()); reporters should subclassParallelBufferedReporterinmocha/lib/nodejs/reporters/parallel-bufferedRunner.prototype.linkPartialObjects()); use if strict object equality is needed when consumingRunnerevent dataRunner.prototype.isParallelMode())🐛 Fixes
npmv6.x causing some of Mocha's deps to be installed whenmochais present in a package'sdevDependenciesandnpm install --productionis run the package's working copy (@boneskull)nycwith Mocha in parallel mode (@boneskull)lookupFiles()inmocha/lib/utils, which was broken/missing in Mocha v8.1.0; it now prints a deprecation warning (useconst {lookupFiles} = require('mocha/lib/cli')instead) (@boneskull)Thanks to @AviVahl, @donghoon-song, @ValeriaVG, @znarf, @sujin-park, and @majecty for other helpful contributions!
v8.1.3Compare Source
🐛 Fixes
Mocha.utils.lookupFiles()and Webpack compatibility (both broken since v8.1.0);Mocha.utils.lookupFiles()is now deprecated and will be removed in the next major revision of Mocha; userequire('mocha/lib/cli').lookupFilesinstead (@boneskull)v8.1.2Compare Source
🐛 Fixes
🔒 Security Fixes
📖 Documentation
v8.1.1Compare Source
🐛 Fixes
v8.1.0Compare Source
In this release, Mocha now builds its browser bundle with Rollup and Babel, which will provide the project's codebase more flexibility and consistency.
While we've been diligent about backwards compatibility, it's possible consumers of the browser bundle will encounter differences (other than an increase in the bundle size). If you do encounter an issue with the build, please report it here.
This release does not drop support for IE11.
Other community contributions came from @Devjeel, @Harsha509 and @sharath2106. Thank you to everyone who contributed to this release!
🎉 Enhancements
🐛 Fixes
mocha init(@boneskull)delayoption in browser (@craigtaub)🔒 Security Fixes
📖 Documentation & Website
--enable-source-mapswith Mocha (@bcoe)🔩 Other
v8.0.1Compare Source
The obligatory patch after a major.
🐛 Fixes
--parallelwhen combined with--watch(@boneskull)v8.0.0Compare Source
In this major release, Mocha adds the ability to run tests in parallel. Better late than never! Please note the breaking changes detailed below.
Let's welcome @giltayar and @nicojs to the maintenance team!
💥 Breaking Changes
#4164: Mocha v8.0.0 now requires Node.js v10.12.0 or newer. Mocha no longer supports the Node.js v8.x line ("Carbon"), which entered End-of-Life at the end of 2019 (@UlisesGascon)
#4175: Having been deprecated with a warning since v7.0.0,
mocha.optsis no longer supported (@juergba)✨ WORKAROUND: Replace
mocha.optswith a configuration file.#4260: Remove
enableTimeout()(this.enableTimeout()) from the context object (@craigtaub)✨ WORKAROUND: Replace usage of
this.enableTimeout(false)in your tests withthis.timeout(0).#4315: The
specoption no longer supports a comma-delimited list of files (@juergba)✨ WORKAROUND: Use an array instead (e.g.,
"spec": "foo.js,bar.js"becomes"spec": ["foo.js", "bar.js"]).#4309: Drop support for Node.js v13.x line, which is now End-of-Life (@juergba)
#4282:
--forbid-onlywill throw an error even if exclusive tests are avoided via--grepor other means (@arvidOtt)#4223: The context object's
skip()(this.skip()) in a "before all" (before()) hook will no longer execute subsequent sibling hooks, in addition to hooks in child suites (@juergba)#4178: Remove previously soft-deprecated APIs (@wnghdcjfe):
Mocha.prototype.ignoreLeaks()Mocha.prototype.useColors()Mocha.prototype.useInlineDiffs()Mocha.prototype.hideDiff()🎉 Enhancements
#4245: Add ability to run tests in parallel for Node.js (see docs) (@boneskull)
❗ See also #4244; Root Hook Plugins (docs) -- root hooks must be defined via Root Hook Plugins to work in parallel mode
#4304:
--requirenow works with ES modules (@JacobLey)#4299: In some circumstances, Mocha can run ES modules under Node.js v10 -- use at your own risk! (@giltayar)
📖 Documentation
🔩 Other
🐛 Fixes
(All bug fixes in Mocha v8.0.0 are also breaking changes, and are listed above)
v7.2.0Compare Source
🎉 Enhancements
🐛 Fixes
--forbid-onlydoes not recognizeit.onlywhenbeforecrashes (@arvidOtt)📖 Documentation
🔩 Other
v7.1.2Compare Source
🔩 Other
📖 Documentation
v7.1.1Compare Source
🔒 Security Fixes
🐛 Fixes
runnerlistening tostartandendevents (@juergba)📖 Documentation
v7.1.0Compare Source
🎉 Enhancements
#4038: Add Node.js native ESM support (@giltayar)
Mocha supports writing your test files as ES modules:
--experimental-modulesoptionNote: Node.JS native ECMAScript Modules implementation has status: Stability: 1 - Experimental
🐛 Fixes
allowUncaughtoption (@juergba)📖 Documentation
package.json(@outsideris)🔩 Other
v7.0.1Compare Source
🐛 Fixes
reporterOptions(@holm)📖 Documentation
🔩 Other
v7.0.0Compare Source
💥 Breaking Changes
--debug/--debug-brkand deprecatedebugargument (@juergba)--list-interfacesreplaces--interfaces--list-reportersreplaces--reportersthis.skip()(@juergba):ittest, relatedafterEachhooks are now executedbeforeEachhook, subsequent innerbeforeEachhooks are now skipped and relatedafterEachhooks are executedthis.skip()withinafterhooksgetOptions()andlib/cli/options.js(@juergba)pendingtest: don't swallow, but retrospectively fail the test for correct exit code (@juergba)Mochaconstructor's option names with command-line options (@juergba)🎉 Enhancements
--watchmode with chokidar (@geigerzaehler):--watch-filesand--watch-ignore--watch-extensions📠 Deprecations
These are soft-deprecated, and will emit a warning upon use. Support will be removed in (likely) the next major version of Mocha:
mocha.opts(@juergba)🐛 Fixes
--inspect-brk/--inspect(@juergba)Mochaconstructor: improve browser setup (@juergba)--allow-uncaughtwiththis.skip()(@juergba)🔍 Coverage
📖 Documentation
done()(@jgehrcke):coffee:with emoji ☕️ (@pzrq)shtobashfor code block in docs/index.md (@HyunSangHan)🔩 Other
package.json(@Munter)v6.2.3Compare Source
🔒 Security Fixes
v6.2.2Compare Source
🐛 Fixes
EVENT_RUN_ENDevents upon uncaught exception (@juergba)htmlreporter (browser) (@pec9399)📖 Documentation
v6.2.1Compare Source
🐛 Fixes
📖 Documentation
v6.2.0Compare Source
🎉 Enhancements
🐛 Fixes
--file(@gabegorelick)globalorglobals(@pascalpp)_mochabinary (@juergba)--timeout/--slowstring values and duplicate arguments (@boneskull, @juergba)📖 Documentation
🔍 Coverage
--watchoptions (@geigerzaehler)🔩 Other
--watchmode behavior (@geigerzaehler)runWatchinto separate module (@geigerzaehler)mocha.min.jsfile to stacktrace filter (@brian-lagerman)--excludeto--ignoreand create alias (@boneskull)mocha.css(@DanielRuf)v6.1.4Compare Source
🔒 Security Fixes
v6.1.3Compare Source
🐛 Fixes
yargs-related global scope pollution (@inukshuk)pnpm(@boneskull)v6.1.2Compare Source
🐛 Fixes
v6.1.1Compare Source
🐛 Fixes
v6.1.0Compare Source
🔒 Security Fixes
🎉 Enhancements
optionsparameter (@plroebuck).jsoncextension (@sstephant)📠 Deprecations
These are soft-deprecated, and will emit a warning upon use. Support will be removed in (likely) the next major version of Mocha:
this.skip()for "after all" hooks (@juergba)🐛 Fixes
this.skip()in "before each" hooks (@juergba)--allow-uncaughtfor uncaught exceptions thrown inside hooks (@givanse)and some regressions:
Suitecloning by copyingrootproperty (@fatso83)📖 Documentation
🔩 Other
v6.0.2Compare Source
🐛 Fixes
Two more regressions fixed:
mocha.opts(@boneskull)--requiredoes not break on module names that look like certainnodeflags (@boneskull)v6.0.1Compare Source
The obligatory round of post-major-release bugfixes.
🐛 Fixes
These issues were regressions.
test.jswhen run without arguments (@plroebuck)--ui(@boneskull)--watch(@boneskull)undefinedvalue from adescribecallback is no longer considered deprecated (@boneskull)📖 Documentation
@mocha/docdash@2(@tendonstrength)v6.0.0Compare Source
🎉 Enhancements
requirecache (@plroebuck)🐛 Fixes
Suite#_onlyTestsandSuite#_onlySuites(@vkarpov15)lookupFilesandfiles(@plroebuck)--delay(and other boolean options) not working in all cases (@boneskull)--reporter-option/--reporter-optionsdid not support comma-separated key/value pairs (@boneskull)📖 Documentation
🔩 Other
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.