objektiv icon indicating copy to clipboard operation
objektiv copied to clipboard

Published 20 hours ago • verified publisher icon nLight

chore(deps): update dependency mocha to v10

Open renovate[bot] opened this issue 2 years ago • 0 comments

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
mocha (source) 8.1.0 -> 10.7.3 age adoption passing confidence

Release Notes

mochajs/mocha (mocha)

v10.7.3

Compare Source

🩹 Fixes

v10.7.0

Compare Source

:tada: Enhancements

v10.6.1

Compare Source

:bug: Fixes

v10.6.0

Compare Source

:tada: Enhancements

v10.5.2

Compare Source

:bug: Fixes

v10.5.1

Compare Source

:bug: Fixes

v10.5.0

Compare Source

:tada: Enhancements
:bug: Fixes
:nut_and_bolt: Other

v10.4.0

Compare Source

:tada: Enhancements
:bug: Fixes
:nut_and_bolt: Other

v10.3.0

Compare Source

This is a stable release equivalent to 10.30.0-prerelease.

v10.2.0

Compare Source

:tada: Enhancements

:bug: Fixes

:book: Documentation

v10.1.0

Compare Source

:tada: Enhancements

:nut_and_bolt: Other

v10.0.0

Compare Source

:boom: Breaking Changes

:nut_and_bolt: Other

Also thanks to @​ea2305 and @​SukkaW for improvements to our documentation.

v9.2.2

Compare Source

:bug: Fixes

:nut_and_bolt: Other

v9.2.1

Compare Source

:bug: Fixes

v9.2.0

Compare Source

:tada: Enhancements

:nut_and_bolt: Other

v9.1.4

Compare Source

:bug: Fixes

:nut_and_bolt: Other

v9.1.3

Compare Source

:bug: Fixes

:nut_and_bolt: Other

v9.1.2

Compare Source

:bug: Fixes

:nut_and_bolt: Other

v9.1.1

Compare Source

:bug: Fixes

v9.1.0

Compare Source

:tada: Enhancements

v9.0.3

Compare Source

:bug: Fixes

v9.0.2

Compare Source

:bug: Fixes

:nut_and_bolt: Other

v9.0.1

Compare Source

:nut_and_bolt: 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.

v9.0.0

Compare Source

:boom: Breaking Changes

Mocha is going ESM-first! This means that it will now use ESM import(test_file) to load the test files, instead of the CommonJS require(test_file). This is not a problem, as import can also load most files that require does. In the rare cases where this fails, it will fallback to require(...). This ESM-first approach is the next step in Mocha's ESM migration, and allows ESM loaders to load and transform the test file.

:tada: Enhancements

:bug: Fixes

:nut_and_bolt: Other

v8.4.0

Compare Source

:tada: Enhancements

:bug: Fixes

:book: Documentation

Also thanks to @​outsideris for various improvements on our GH actions workflows.

v8.3.2

Compare Source

:bug: Fixes

:book: Documentation

v8.3.1

Compare Source

:bug: Fixes

v8.3.0

Compare Source

:tada: Enhancements

:bug: Fixes

:book: Documentation

:nut_and_bolt: Other

Also thanks to @​outsideris and @​HyunSangHan for various fixes to our website and documentation.

v8.2.1

Compare Source

Fixed stuff.

:bug: Fixes

  • #​4489: Fix problematic handling of otherwise-unhandled Promise rejections and erroneous "done() called twice" errors (@​boneskull)
  • #​4496: Avoid 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-level before() 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.js

// can be async or not
exports.mochaGlobalSetup = async function() {
  this.server = await startSomeServer({port: process.env.TEST_PORT});
  console.log(`server running on port ${this.server.port}`);
};

exports.mochaGlobalTeardown = async function() {
  // the context (`this`) is shared, but not with the test files
  await this.server.stop();
  console.log(`server on port ${this.server.port} stopped`);
};

// this file can contain root hook plugins as well!
// exports.mochaHooks = { ... }

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).

:tada: Enhancements

For implementors of custom reporters:

  • #​4409: Parallel mode and custom reporter improvements (@​boneskull):
    • Support custom worker-process-only reporters (Runner.prototype.workerReporter()); reporters should subclass ParallelBufferedReporter in mocha/lib/nodejs/reporters/parallel-buffered
    • Allow opt-in of object reference matching for "sufficiently advanced" custom reporters (Runner.prototype.linkPartialObjects()); use if strict object equality is needed when consuming Runner event data
    • Enable detection of parallel mode (Runner.prototype.isParallelMode())

:bug: Fixes

  • #​4476: Workaround for profoundly bizarre issue affecting npm v6.x causing some of Mocha's deps to be installed when mocha is present in a package's devDependencies and npm install --production is run the package's working copy (@​boneskull)
  • #​4465: Worker processes guaranteed (as opposed to "very likely") to exit before Mocha does; fixes a problem when using nyc with Mocha in parallel mode (@​boneskull)
  • #​4419: Restore lookupFiles() in mocha/lib/utils, which was broken/missing in Mocha v8.1.0; it now prints a deprecation warning (use const {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

:bug: Fixes

  • #​4425: Restore 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; use require('mocha/lib/cli').lookupFiles instead (@​boneskull)

v8.1.2

Compare Source

:bug: Fixes

:lock: Security Fixes

:book: Documentation

v8.1.1

Compare Source

:bug: Fixes

  • #​4394: Fix regression wherein certain reporters did not correctly detect terminal width (@​boneskull)

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • [ ] If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate[bot] avatar May 15 '22 22:05 renovate[bot]