Update JS unit test packages (major) #237
Open
+397
−352
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:
^8.0.1
->^10.0.0
^8.1.1
->^11.0.0
Release Notes
mochajs/mocha (mocha)
v11.0.1
Compare Source
🌟 Features
📚 Documentation
linkPartialObjects
methods (#5255) (34e0e52)v11.0.0
Compare Source
⚠ BREAKING CHANGES
🌟 Features
🩹 Fixes
📚 Documentation
v10.8.2
Compare Source
🩹 Fixes
📚 Documentation
🧹 Chores
🤖 Automation
v10.8.1
Compare Source
🩹 Fixes
v10.8.0
Compare Source
🌟 Features
🩹 Fixes
:is()
frommocha.css
to support older browsers (#5225) (#5227) (0a24b58)📚 Documentation
SECURITY.md
pointing to Tidelift (#5210) (bd7e63a)🧹 Chores
v10.7.3
Compare Source
🩹 Fixes
v10.7.0
Compare Source
🎉 Enhancements
v10.6.1
Compare Source
🐛 Fixes
v10.6.0
Compare Source
🎉 Enhancements
v10.5.2
Compare Source
🐛 Fixes
v10.5.1
Compare Source
🐛 Fixes
v10.5.0
Compare Source
🎉 Enhancements
🐛 Fixes
🔩 Other
v10.4.0
Compare Source
🎉 Enhancements
.cause
stacks in the error stack traces (@voxpelli)🐛 Fixes
lib/cli/run.js
(@stalet)🔩 Other
v10.3.0
Compare Source
This is a stable release equivalent to 10.30.0-prerelease.
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
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.