Packages

process-warning

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

Upgrading process-warning From 2.0.0 to 5.1.1

11 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 2.0.0Newest 2.x2.3.2
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.0.0yours
  2. 5 releases
  3. 3.0.0major
  4. 4.0.0major
  5. 1 release
  6. 5.0.0major
  7. 1 release
  8. 5.1.1target
?
changes to make
0
advisories fixed
5
new
1
fix

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. 2.3.2 – 4.0.03 releases, nothing new or fixed in the notes

  6. 2.3.1

    18 Nov 20231 fix
    • Fixed

      Avoid global unlimited config

  7. 2.3.0

    27 Oct 20231 new
    • New

      Add createDeprecation method

  8. 2.2.0

    4 Apr 20231 new
    • New

      Add unlimited option

7 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
  • Revert 2.3.1

    2.3.2
  • Use constants instead of magic numbers

    2.3.1
  • Use tap instead of ava, 100% test coverage, move types to types folder, activate linting in ci-pipeline

    2.1.0
  • Nodenext compatibility

    2.1.0

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