process-warning
5.1.1 · 10 Oct 2026MIT94.6M / weekRepositoryHomepagenpmAtom feed
Upgrading process-warning From 1.0.0 to 5.1.1
12 releases in betweenevery note read
Reading releases, release notes and advisories…
Release by release
5.1.1nothing new or fixed in the note
- New
Allow spy warning and return emitted state
- New
5.0.0nothing new or fixed in the note
- New
Use
node:prefix to bypass require.cache call for builtins
- New
2.3.2 – 4.0.03 releases, nothing new or fixed in the notes
- Fixed
Avoid global unlimited config
- Fixed
- New
Add createDeprecation method
- New
- New
Add unlimited option
- New
7 other lines we could not sort, mostly version bumps
- 4.0.0
Update README.md
- 4.0.0
Merge
nextintomaster - 3.0.0
Refactoring (v3)
- 2.3.2
Revert 2.3.1
- 2.3.1
Use constants instead of magic numbers
- 2.1.0
Use tap instead of ava, 100% test coverage, move types to types folder, activate linting in ci-pipeline
- 2.1.0
Nodenext compatibility
68 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.