Bump mocha from 8.1.3 to 8.3.0

[dependabot]

Bumps mocha from 8.1.3 to 8.3.0.

Release notes

Sourced from mocha's releases.

v8.3.0

8.3.0 / 2021-02-11

🎉 Enhancements

• #4506: Add error code for test timeout errors (@boneskull)
• #4112: Add BigInt support to stringify util function (@JosejeSinohui)

🐛 Fixes

• #4557: Add file location when SyntaxError happens in ESM (@giltayar)
• #4521: Fix require error when bundling Mocha with Webpack (@devhazem)

📖 Documentation

• #4507: Add support for typescript-style docstrings (@boneskull)
• #4503: Add GH Actions workflow status badge (@outsideris)
• #4494: Add example of generating tests dynamically with a closure (@maxwellgerber)

🔩 Other

• #4556: Upgrade all dependencies to latest stable (@AviVahl)
• #4543: Update dependencies yargs and yargs-parser (@juergba)

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

v8.2.1

8.2.1 / 2020-11-02

Fixed stuff.

🐛 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

8.2.0 / 2020-10-16

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:

</tr></table> 

... (truncated)

Changelog

Sourced from mocha's changelog.

8.3.0 / 2021-02-11

🎉 Enhancements

• #4506: Add error code for test timeout errors (@boneskull)
• #4112: Add BigInt support to stringify util function (@JosejeSinohui)

🐛 Fixes

• #4557: Add file location when SyntaxError happens in ESM (@giltayar)
• #4521: Fix require error when bundling Mocha with Webpack (@devhazem)

📖 Documentation

• #4507: Add support for typescript-style docstrings (@boneskull)
• #4503: Add GH Actions workflow status badge (@outsideris)
• #4494: Add example of generating tests dynamically with a closure (@maxwellgerber)

🔩 Other

• #4556: Upgrade all dependencies to latest stable (@AviVahl)
• #4543: Update dependencies yargs and yargs-parser (@juergba)

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

8.2.1 / 2020-11-02

Fixed stuff.

🐛 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!

8.2.0 / 2020-10-16

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
</tr></table>

... (truncated)

Commits

• e1194ab Release v8.3.0
• 9e75153 update CHANGELOG for v8.3.0 [ci skip]
• 6dd12be match supporter's properties with supporter.js (#4569)
• 9f2dd41 docs: add example of generating tests with a closure (#4494)
• 9122909 Adds BigInt support to stringify util function (#4112)
• 9878f32 Add file location when SyntaxError happens in ESM (#4557)
• 84d0c96 Deps: update workerpool (#4566)
• 3c2f82f GH actions: purge-expired-artifacts.yml (#4565)
• 1a05ad7 chore(deps): upgrade all to latest stable (#4556)
• c667d10 docs: fix javascript syntax errors (#4555)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)