Packages

debug

4.4.3 · 13 Sep 2025MIT930.4M / weekRepositoryHomepagenpmAtom feed

Upgrading debug From 4.3.0 to 4.4.3

11 releases in betweennotes for 10

Other targets from 4.3.0Clears its advisory4.3.1
  1. 4.3.0yours
  2. 4.3.1security
  3. 9 releases
  4. 4.4.3target
?
changes to make
1
advisory fixed
2+
new
9+
fixes

Counted from 10 of 11 release notes. Advisories are counted from the advisory database, in full.

Start here

Security

Fixes 1 advisory affecting 4.3.0

  • Fixes a ReDOS regression (#458) - see #797 for details.

    4.3.1

Release by release

  1. 4.4.2 – 4.4.32 releases, nothing new or fixed; 1 without a note

  2. 4.4.1

    13 May 20252 fixes
    • fixed

      Issue-996: Replace whitespaces in namespaces string with commas globally

    • fixed

      Fixes #987 fallback to localStorage.DEBUG if debug is not defined

  3. 4.3.7 – 4.4.02 releases, nothing new or fixed in the notes

  4. 4.3.6

    27 Jul 20241 fix
    • fixed

      Avoid using deprecated RegExp.$1

  5. 4.3.5

    31 May 20241 fix
    • fixed

      Fix/debug depth

  6. 4.3.4

    17 Mar 20221 new
    • new

      Add section about configuring JS console to show debug messages

  7. 4.3.3

    27 Nov 20211 new · 4 fixes
    • new

      Adds README section regarding usage in child procs

    • fixed

      Migrates repository from github.com/visionmedia/debug to github.com/debug-js/debug. Please see notes below as to why this change was made.

    • fixed

      Updates repository maintainership information

    • fixed

      Updates the copyright (no license terms change has been made)

    • fixed

      Removes accidental epizeuxis

  8. 4.3.2

    9 Dec 20201 fix
    • fixed

      Caches enabled statuses on a per-logger basis to speed up .enabled checks

6 other lines we could not sort, mostly version bumps

  • Upgrade ms to version 2.1.3

    4.3.7

  • Replace deprecated String.prototype.substr()

    4.3.4

  • The old organization was defunct and abandoned.

    4.3.3

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

    4.3.3

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

    4.3.3

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

    4.3.3