Packages

process-warning

5.1.1 · 10 Oct 2026MIT94.6M / weekRepositoryHomepagenpmAtom feed

Upgrading process-warning From 2.3.2 to 5.1.1

6 releases in betweenevery note read

Reading releases, release notes and advisories…

The notes of 5.0.0, 4.0.0, 3.0.0 list no breaking change or deprecation, which is rare for a major.
  1. 2.3.2yours
  2. 3.0.0major
  3. 4.0.0major
  4. 4.0.1
  5. 5.0.0major
  6. 5.1.0
  7. 5.1.1target
?
changes to make
0
advisories fixed
2
new
0
fixes

Release by release

  1. 5.1.1nothing new or fixed in the note

  2. 5.1.0

    30 Jul 20261 new
    • New

      Allow spy warning and return emitted state

  3. 5.0.0nothing new or fixed in the note

  4. 4.0.1

    3 Jan 20251 new
    • New

      Use node: prefix to bypass require.cache call for builtins

  5. 3.0.0 – 4.0.02 releases, nothing new or fixed in the notes

3 other lines we could not sort, mostly version bumps
  • Update README.md

    4.0.0
  • Merge next into master

    4.0.0
  • Refactoring (v3)

    3.0.0

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

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.