Packages

process-warning

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

Upgrading process-warning From 4.0.0 to 5.1.1

4 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 4.0.0Newest 4.x4.0.1
The note of 5.0.0 lists no breaking change or deprecation, which is rare for a major.
?
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

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