chore(deps): update dependency debug to v4.4.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
debug	4.3.2 → 4.4.3

---

Release Notes

debug-js/debug (debug)

v4.4.3

Compare Source

Functionally identical release to 4.4.1.

Version 4.4.2 is compromised. Please see #​1005.

v4.4.1

Compare Source

What's Changed

• fix(Issue-996): replace whitespaces in namespaces string with commas globally by @​pdahal-cx in #​997
• fixes #​987 fallback to localStorage.DEBUG if debug is not defined by @​lzilioli in #​988

New Contributors

• @​pdahal-cx made their first contribution in #​997
• @​lzilioli made their first contribution in #​988

Full Changelog: debug-js/debug@4.4.0...4.4.1

v4.4.0

Compare Source

Fixes (hopefully) the inefficient regex warnings in .enable().

Minor version as this is invariably going to break certain users who misuse the .enable() API and expected it to work with regexes, which was never supported nor documented. That's on you, sorry - that functionality won't be added back.

Full Changelog: debug-js/debug@4.3.7...4.4.0

v4.3.7

Compare Source

What's Changed

• Upgrade ms to version 2.1.3 by @​realityking in #​819

Full Changelog: debug-js/debug@4.3.6...4.3.7

v4.3.6

Compare Source

What's Changed

• Avoid using deprecated RegExp.$1 by @​bluwy in #​969

New Contributors

• @​bluwy made their first contribution in #​969

Full Changelog: debug-js/debug@4.3.5...4.3.6

v4.3.5

Compare Source

Patch

• cac39b1 Fix/debug depth (#​926)

Thank you @​calvintwr for the fix.

v4.3.4

Compare Source

What's Changed

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

New Contributors

• @​gitname made their first contribution in #​866
• @​CommanderRoot made their first contribution in #​876

Full Changelog: debug-js/debug@4.3.3...4.3.4

v4.3.3

Compare Source

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.

I understand there are a lot of edge cases so please open issues as needed so I can assist in any way necessary.

Q: Why was the repository transferred?

I'll just list them off in no particular order.

• The old organization was defunct and abandoned.
• I was not an owner of the old organization and thus could not ban the non-trivial amount of spam users or the few truly abusive users from the org. This hindered my ability to properly maintain this package.
• The debug ecosystem intends to grow beyond a single package, and since new packages could not be created in the old org (nor did it make sense for them to live there), a new org made the most sense - especially from a security point of view.
• The old org has way, way too many approved members with push access, for which there was nothing I could do. This presented a pretty sizable security risk given that many packages in recent years have fallen victim to backdoors and the like due to lax security access.

Q: Was this approved?

Yes.^[archive]

Q: Do I need to worry about another migration sometime in the future?

No.

---

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]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit