Bump debug, mocha and vscode in /xvscMisc

[dependabot[bot]]

Bumps debug to 4.3.4 and updates ancestor dependencies debug, mocha and vscode. These dependencies need to be updated together.

Updates debug from 2.2.0 to 4.3.4

Release notes

Sourced from debug's releases.

4.3.4

What's Changed

• Add section about configuring JS console to show debug messages by @​gitname in debug-js/debug#866
• Replace deprecated String.prototype.substr() by @​CommanderRoot in debug-js/debug#876

New Contributors

• @​gitname made their first contribution in debug-js/debug#866
• @​CommanderRoot made their first contribution in debug-js/debug#876

Full Changelog: https://github.com/debug-js/debug/compare/4.3.3...4.3.4

4.3.3

Patch Release 4.3.3

This is a documentation-only release. Further, the repository was transferred. Please see notes below.

• Migrates repository from https://github.com/visionmedia/debug to https://github.com/debug-js/debug. Please see notes below as to why this change was made.
• Updates repository maintainership information
• Updates the copyright (no license terms change has been made)
• Removes accidental epizeuxis (#828)
• Adds README section regarding usage in child procs (#850)

Thank you to @​taylor1791 and @​kristofkalocsai for their contributions.

---

Repository Migration Information

I've formatted this as a FAQ, please feel free to open an issue for any additional question and I'll add the response here.

Q: What impact will this have on me?

In most cases, you shouldn't notice any change.

The only exception I can think of is if you pull code directly from https://github.com/visionmedia/debug, e.g. via a "debug": "visionmedia/debug"-type version entry in your package.json - in which case, you should still be fine due to the automatic redirection Github sets up, but you should also update any references as soon as possible.

Q: What are the security implications of this change?

If you pull code directly from the old URL, you should update the URL to https://github.com/debug-js/debug as soon as possible. The old organization has many approved owners and thus a new repository could (in theory) be created at the old URL, circumventing Github's automatic redirect that is in place now and serving malicious code. I (@​qix-) also wouldn't have access to that repository, so while I don't think it would happen, it's still something to consider.

Even in such a case, however, the officially released package on npm (debug) would not be affected. That package is still very much under control (even more than it used to be).

Q: What should I do if I encounter an issue related to the migration?

Search the issues first to see if someone has already reported it, and then open a new issue if someone has not.

Q: Why was this done as a 'patch' release? Isn't this breaking?

No, it shouldn't be breaking. The package on npm shouldn't be affected (aside from this patch release) and any references to the old repository should automatically redirect.

Thus, according to all of the "APIs" (loosely put) involved, nothing should have broken.

... (truncated)

Commits

• da66c86 4.3.4
• 9b33412 replace deprecated String.prototype.substr() (#876)
• c0805cc add section about configuring JS console to show debug messages (#866)
• 043d3cd 4.3.3
• 4079aae update license and more maintainership information
• 19b36c0 update repository location + maintainership information
• f851b00 adds README section regarding usage in child procs (#850)
• d177f2b Remove accidental epizeuxis
• e47f96d 4.3.2
• 1e9d38c cache enabled status per-logger (#799)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by qix, a new releaser for debug since your current version.

Updates mocha from 2.5.3 to 10.2.0

Release notes

Sourced from mocha's releases.

v10.2.0

10.2.0 / 2022-12-11

:tada: Enhancements

• #4945: API: add possibility to decorate ESM name before import (@​j0tunn)

:bug: Fixes

• #4946: Browser: color of failed test icon (@​kleisauke)

:book: Documentation

• #4944: Remove duplicated header (@​PauloGoncalvesBH)

v10.1.0

10.1.0 / 2022-10-16

:tada: Enhancements

• #4896: Browser: add support for prefers-color-scheme: dark (@​greggman)

:nut_and_bolt: Other

• #4912: Browser: increase contrast for replay buttons (@​JoshuaKGoldberg)
• #4905: Use standard Promise.allSettled instead of polyfill (@​outsideris)
• #4899: Upgrade official GitHub actions to latest (@​ddzz)
• #4770: Fix regex in function clean(@​yetingli)

v10.0.0

10.0.0 / 2022-05-01

:boom: 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 to bin/mocha.js (@​juergba)

• #4865: --ignore option in Windows: upgrade Minimatch (@​juergba)

• #4861: Remove deprecated Runner signature (@​juergba)

:nut_and_bolt: Other

... (truncated)

Changelog

Sourced from mocha's changelog.

10.2.0 / 2022-12-11

:tada: Enhancements

• #4945: API: add possibility to decorate ESM name before import (@​j0tunn)

:bug: Fixes

• #4946: Browser: color of failed test icon (@​kleisauke)

:book: Documentation

• #4944: Remove duplicated header (@​PauloGoncalvesBH)

10.1.0 / 2022-10-16

:tada: Enhancements

• #4896: Browser: add support for prefers-color-scheme: dark (@​greggman)

:nut_and_bolt: Other

• #4912: Browser: increase contrast for replay buttons (@​JoshuaKGoldberg)
• #4905: Use standard Promise.allSettled instead of polyfill (@​outsideris)
• #4899: Upgrade official GitHub actions to latest (@​ddzz)
• #4770: Fix regex in function clean(@​yetingli)

10.0.0 / 2022-05-01

:boom: 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 to bin/mocha.js (@​juergba)

• #4865: --ignore option in Windows: upgrade Minimatch (@​juergba)

• #4861: Remove deprecated Runner signature (@​juergba)

:nut_and_bolt: Other

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

• #4876: Add Node.js v18 to CI test matrix (@​outsideris)

... (truncated)

Commits

• 202e9b8 build(v10.2.0): release
• 6782d6d build(v10.2.0): update CHANGELOG
• 73bb819 feat(esm): ability to decorate ESM module name before importing it (#4945)
• fc4ac58 chore(devDeps): remove unused depedencies (#4949)
• 0a10ddc docs: remove duplicated header (#4944)
• b0a0fb8 fix(browser): failed test icon color (#4946)
• 3cc9cac ci: update stale action (#4931)
• 8f3c37b chore(ci): workaround for firefox error (#4933)
• 5f96d51 build(v10.1.0): release
• ed74f16 build(v10.1.0): update CHANGELOG
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by juergba, a new releaser for mocha since your current version.

Updates vscode from 1.1.5 to 1.1.37

Commits

• c871436 v1.1.37
• e55dfe8 Clean up for new release
• faa0254 Merge pull request #170 from microsoft/pine/154
• 71ff0ef Fix #154
• 216c61a Merge pull request #169 from microsoft/dependabot/npm_and_yarn/https-proxy-ag...
• e1e0c6c Bump https-proxy-agent from 2.2.1 to 2.2.4
• 0090df8 v1.1.36
• 50e9a97 Add a migration notice
• 1688fb3 Use an accurate repository field in package.json (#160)
• f6fef4d v1.1.35
• 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.