Bump mocha from 7.1.2 to 9.0.3

[dependabot-preview]

Bumps mocha from 7.1.2 to 9.0.3.

Release notes

Sourced from mocha's releases.

v9.0.3

9.0.3 / 2021-07-25

🐛 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 of type:module (@​giltayar)

v9.0.2

9.0.2 / 2021-07-03

🐛 Fixes

• #4668: ESM: make --require <dir> work with new import-first loading (@​giltayar)

🔩 Other

• #4674: Update production dependencies (@​juergba)

v9.0.1

9.0.1 / 2021-06-18

🔩 Other

• #4657: Browser: add separate bundle for modern browsers (@​juergba)

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.

• #4653: ESM: proper version check in hasStableEsmImplementation (@​alexander-fenster)

v9.0.0

9.0.0 / 2021-06-07

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

• #4636: Remove deprecated utils.lookupFiles() (@​juergba)

• #4638: Limit the size of actual/expected for diff generation (@​juergba)

• #4389: Refactoring: Consuming log-symbols alternate to code for win32 in reporters/base (@​MoonSupport)

... (truncated)

Changelog

Sourced from mocha's changelog.

9.0.3 / 2021-07-25

🐛 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 of type:module (@​giltayar)

9.0.2 / 2021-07-03

🐛 Fixes

• #4668: ESM: make --require <dir> work with new import-first loading (@​giltayar)

🔩 Other

• #4674: Update production dependencies (@​juergba)

9.0.1 / 2021-06-18

🔩 Other

• #4657: Browser: add separate bundle for modern browsers (@​juergba)

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.

• #4653: ESM: proper version check in hasStableEsmImplementation (@​alexander-fenster)

9.0.0 / 2021-06-07

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

• #4636: Remove deprecated utils.lookupFiles() (@​juergba)

• #4638: Limit the size of actual/expected for diff generation (@​juergba)

• #4389: Refactoring: Consuming log-symbols alternate to code for win32 in reporters/base (@​MoonSupport)

🎉 Enhancements

• #4640: Add new option --dry-run (@​juergba)

... (truncated)

Commits

• e044ef0 Release v9.0.3
• 8907601 update CHANGELOG for v9.0.3 [ci skip]
• 7313890 Fix exception rethrow from js config file (#4702)
• 3722201 Fix: using custom interface in parallel mode (#4688)
• 6830821 ESM: fix swallowing MODULE_NOT_FOUND errors in case of type:module (#4687)
• 5c59da0 Release v9.0.2
• 0ce3528 update CHANGELOG for v9.0.2 [ci skip]
• ff51a77 Update production dependencies (#4674)
• 21cda3e Make "-r <dir>" work with new import-first loading (#4668)
• f033ff1 Fix: karma-mocha should run both browser bundles (#4663)
• 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)
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

• Update frequency
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)