debug

4.4.3 · 13 Sep 2025MIT930.4M / weekRepository Homepage npm Atom feed

Upgrading debug From 2.6.9 to 3.0.0

Same major only

1 release in betweenevery note read

Other targets from 2.6.9Latest4.4.3

2.6.9yours
3.0.0target

4
changes to make: 0
advisories fixed: 8
new: 1
fix

Before you upgrade

Tick each one off as you go

Remove DEBUG_FD
breaking3.0.0
Make millisecond timer namespace specific and allow 'always enabled' output
breaking3.0.0
Use Date#toISOString() instead to Date#toUTCString() when output is not a TTY
breaking3.0.0
enabled() updates existing debug instances
breaking3.0.0

Security

2 advisories still affect 3.0.0

debug Inefficient Regular Expression Complexity vulnerabilityhigh · GHSA-9vvw-cc9w-f27h
Regular Expression Denial of Service in debuglow · GHSA-gxpj-cx7g-858c

Upgrading to 3.1.0 clears them.

Release by release

3.0.0
Migration needed8 Aug 20178 new · 1 fix
- breaking
  Remove DEBUG_FD
- breaking
  Make millisecond timer namespace specific and allow 'always enabled' output
- breaking
  Use Date#toISOString() instead to Date#toUTCString() when output is not a TTY
- breaking
  enabled() updates existing debug instances

2 internal lines (docs, tests, tooling) left out.

Upgrade to 3.0.0

npm install debug@3.0.0

What 3.0.0 needs

Reading 3.0.0's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 3.0.0. Read once, not stored.

After upgrading

Run the type checker, the linter and the tests.
Build, and look for new deprecation warnings.
Update peer dependencies the new version asks for.
2 advisories still affect 3.0.0.