proc-log
7.0.0 · 8 May 2026ISC85.7M / weekRepositoryHomepagenpmAtom feed
Where each line stands
Plan an upgradeLatest releases
- 7.x · latest line
7.0.0
8 May 2026- Breaking
proc-lognow supports node^22.22.2 || ^24.15.0 || >=26.0.0 - Breaking
template-oss-apply
Bump to new node engine range
Breaking changes
- Breaking
proc-lognow supports node^22.22.2 || ^24.15.0 || >=26.0.0 - Breaking
template-oss-apply
Features
Bump to new node engine range
template-oss-apply
- 6.x · maintenance
6.1.0
25 Nov 2025Support args for input
Features
Support args for input
6.0.0
22 Oct 2025- Breaking
proc-lognow supports node^20.17.0 || >=22.9.0 Align to npm 11 node engine range
Breaking changes
- Breaking
proc-lognow supports node^20.17.0 || >=22.9.0
Bug Fixes
Align to npm 11 node engine range
Dependency tracking
Know when your own dependencies move
proc-log shipped a new major in the last 12 months, among 2 releases. inlinr shows which of your projects are behind, and what the upgrade breaks.
Advisories reach you
An email when a critical or high advisory affects a project, before the next install.
Upgrades checked first
Peer ranges, Node, ESM-only and types changes read before you bump.
Only what matters
Majors and breaking notes stay; patches and sibling bumps fold into one line.
Reading releases, release notes and advisories…
Registry facts last checked 20 Nov 2026. Releases and advisories last read 20 Nov 2026.
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.