chore(deps): update dependency mocha to v10 #56
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:
^4.1.0
->^10.0.0
Release Notes
mochajs/mocha (mocha)
v10.2.0
Compare Source
🎉 Enhancements
🐛 Fixes
📖 Documentation
v10.1.0
Compare Source
🎉 Enhancements
prefers-color-scheme: dark
(@greggman)🔩 Other
Promise.allSettled
instead of polyfill (@outsideris)clean
(@yetingli)v10.0.0
Compare Source
💥 Breaking Changes
#4845: Drop Node.js v12.x support (@juergba)
#4848: Drop Internet-Explorer-11 support (@juergba)
#4857: Drop AMD/RequireJS support (@juergba)
#4866: Drop Growl notification support (@juergba)
#4863: Rename executable
bin/mocha
tobin/mocha.js
(@juergba)#4865:
--ignore
option in Windows: upgrade Minimatch (@juergba)#4861: Remove deprecated
Runner
signature (@juergba)🔩 Other
#4878: Update production dependencies (@juergba)
#4876: Add Node.js v18 to CI test matrix (@outsideris)
#4852: Replace deprecated
String.prototype.substr()
(@CommanderRoot)Also thanks to @ea2305 and @SukkaW for improvements to our documentation.
v9.2.2
Compare Source
🐛 Fixes
#4842: Loading of reporter throws wrong error (@juergba)
#4839:
dry-run
: prevent potential call-stack crash (@juergba)🔩 Other
v9.2.1
Compare Source
🐛 Fixes
#4832: Loading of config files throws wrong error (@juergba)
#4799: Reporter: configurable
maxDiffSize
reporter-option (@norla)v9.2.0
Compare Source
🎉 Enhancements
🔩 Other
v9.1.4
Compare Source
🐛 Fixes
import
throws wrong error if loader is used (@giltayar)🔩 Other
v9.1.3
Compare Source
🐛 Fixes
bdd
ES6 style import (@juergba)🔩 Other
EVENT_SUITE_ADD_*
events (@beatfactor)v9.1.2
Compare Source
🐛 Fixes
browser-entry.js
(@PaperStrike)🔩 Other
v9.1.1
Compare Source
🐛 Fixes
XUNIT
andJSON
reporter crash inparallel
mode (@curtisman)v9.1.0
Compare Source
🎉 Enhancements
--fail-zero
(@juergba)--node-option
(@juergba)JSON
reporter (@dorny)v9.0.3
Compare Source
🐛 Fixes
#4702: Error rethrow from cwd-relative path while loading
.mocharc.js
(@kirill-golovan)#4688: Usage of custom interface in parallel mode (@juergba)
#4687: ESM: don't swallow
MODULE_NOT_FOUND
errors in case oftype:module
(@giltayar)v9.0.2
Compare Source
🐛 Fixes
--require <dir>
work with newimport
-first loading (@giltayar)🔩 Other
v9.0.1
Compare Source
🔩 Other
We added a separate browser bundle
mocha-es2018.js
in javascript ES2018, as we skipped the transpilation down to ES5. This is an experimental step towards freezing Mocha's support of IE11.hasStableEsmImplementation
(@alexander-fenster)v9.0.0
Compare 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, asimport
can also load most files thatrequire
does. 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
/expected
fordiff
generation (@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.0
Compare Source
🎉 Enhancements
🐛 Fixes
📖 Documentation
options.require
to Mocha constructor forroot hook
plugins on parallel runs (@juergba)top-level await
and ESM test files (@juergba)Also thanks to @outsideris for various improvements on our GH actions workflows.
v8.3.2
Compare Source
🐛 Fixes
require
interface (@alexander-fenster)📖 Documentation
v8.3.1
Compare Source
🐛 Fixes
EvalError
caused by regenerator-runtime (@snoack)import
from mocha in parallel mode (@nicojs)v8.3.0
Compare Source
🎉 Enhancements
🐛 Fixes
require
error when bundling Mocha with Webpack (@devhazem)📖 Documentation
🔩 Other
Also thanks to @outsideris and @HyunSangHan for various fixes to our website and documentation.
v8.2.1
Compare Source
Fixed stuff.
🐛 Fixes
Promise
rejections and erroneous "done()
called twice" errors (@boneskull)MaxListenersExceededWarning
in watch mode (@boneskull)Also thanks to @akeating for a documentation fix!
v8.2.0
Compare 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--extension
option (@jordanstephens).js
,.test.js
) now usable with--extension
option (@boneskull)json
reporter now containsspeed
("fast"/"medium"/"slow") property (@wwhurin)For implementors of custom reporters:
Runner.prototype.workerReporter()
); reporters should subclassParallelBufferedReporter
inmocha/lib/nodejs/reporters/parallel-buffered
Runner.prototype.linkPartialObjects()
); use if strict object equality is needed when consumingRunner
event dataRunner.prototype.isParallelMode()
)🐛 Fixes
npm
v6.x causing some of Mocha's deps to be installed whenmocha
is present in a package'sdevDependencies
andnpm install --production
is run the package's working copy (@boneskull)nyc
with 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.3
Compare 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').lookupFiles
instead (@boneskull)v8.1.2
Compare Source
🐛 Fixes
🔒 Security Fixes
📖 Documentation
v8.1.1
Compare Source
🐛 Fixes
v8.1.0
Compare 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)delay
option in browser (@craigtaub)🔒 Security Fixes
📖 Documentation & Website
--enable-source-maps
with Mocha (@bcoe)🔩 Other
v8.0.1
Compare Source
The obligatory patch after a major.
🐛 Fixes
--parallel
when combined with--watch
(@boneskull)v8.0.0
Compare 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.opts
is no longer supported (@juergba)✨ WORKAROUND: Replace
mocha.opts
with 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
spec
option 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-only
will throw an error even if exclusive tests are avoided via--grep
or 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:
--require
now 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.0
Compare Source
🎉 Enhancements
🐛 Fixes
--forbid-only
does not recognizeit.only
whenbefore
crashes (@arvidOtt)📖 Documentation
🔩 Other
v7.1.2
Compare Source
🔩 Other
📖 Documentation
v7.1.1
Compare Source
🔒 Security Fixes
🐛 Fixes
runner
listening tostart
andend
events (@juergba)📖 Documentation
v7.1.0
Compare Source
🎉 Enhancements
#4038: Add Node.js native ESM support (@giltayar)
Mocha supports writing your test files as ES modules:
--experimental-modules
optionNote: Node.JS native ECMAScript Modules implementation has status: Stability: 1 - Experimental
🐛 Fixes
allowUncaught
option (@juergba)📖 Documentation
package.json
(@outsideris)🔩 Other
v7.0.1
Compare Source
🐛 Fixes
reporterOptions
(@holm)📖 Documentation
🔩 Other
v7.0.0
Compare Source
💥 Breaking Changes
--debug
/--debug-brk
and deprecatedebug
argument (@juergba)--list-interfaces
replaces--interfaces
--list-reporters
replaces--reporters
this.skip()
(@juergba):it
test, relatedafterEach
hooks are now executedbeforeEach
hook, subsequent innerbeforeEach
hooks are now skipped and relatedafterEach
hooks are executedthis.skip()
withinafter
hooksgetOptions()
andlib/cli/options.js
(@juergba)pending
test: don't swallow, but retrospectively fail the test for correct exit code (@juergba)Mocha
constructor's option names with command-line options (@juergba)🎉 Enhancements
--watch
mode with chokidar (@geigerzaehler):--watch-files
and--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)Mocha
constructor: improve browser setup (@juergba)--allow-uncaught
withthis.skip()
(@juergba)🔍 Coverage
📖 Documentation
done()
(@jgehrcke):coffee:
with emoji ☕️ (@pzrq)sh
tobash
for code block in docs/index.md (@HyunSangHan)🔩 Other
package.json
(@Munter)v6.2.3
Compare Source
🔒 Security Fixes
v6.2.2
Compare Source
🐛 Fixes
EVENT_RUN_END
events upon uncaught exception (@juergba)html
reporter (browser) (@pec9399)📖 Documentation
v6.2.1
Compare Source
🐛 Fixes
📖 Documentation
v6.2.0
Compare Source
🎉 Enhancements
🐛 Fixes
--file
(@gabegorelick)global
orglobals
(@pascalpp)_mocha
binary (@juergba)--timeout
/--slow
string values and duplicate arguments (@boneskull, @juergba)📖 Documentation
🔍 Coverage
--watch
options (@geigerzaehler)🔩 Other
--watch
mode behavior (@geigerzaehler)runWatch
into separate module (@geigerzaehler)mocha.min.js
file to stacktrace filter (@brian-lagerman)--exclude
to--ignore
and create alias (@boneskull)mocha.css
(@DanielRuf)v6.1.4
Compare Source
🔒 Security Fixes
v6.1.3
Compare Source
🐛 Fixes
yargs
-related global scope pollution (@inukshuk)pnpm
(@boneskull)v6.1.2
Compare Source
🐛 Fixes
v6.1.1
Compare Source
🐛 Fixes
v6.1.0
Compare Source
🔒 Security Fixes
🎉 Enhancements
options
parameter (@plroebuck).jsonc
extension (@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)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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 Mend Renovate. View repository job log here.