Packages

process-warning

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

Upgrading process-warning From 2.0.0 to 2.3.2

5 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 2.0.0Latest5.1.1
0
changes to make
0
advisories fixed
4
new
1
fix

Release by release

  1. 2.3.2nothing new or fixed in the note

  2. 2.3.1

    18 Nov 20231 fix
    • Fixed

      Avoid global unlimited config

  3. 2.3.0

    27 Oct 20232 new
    • New

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

    • New

      Add createDeprecation method

  4. 2.2.0

    4 Apr 20231 new
    • New

      Add unlimited option

  5. 2.1.0

    4 Dec 20221 new
    • New

      Improve performance of emit()

4 other lines we could not sort, mostly version bumps
  • 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

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