read-pkg
10.1.0 · 8 Feb 2026MIT65.1M / weekRepositoryHomepagenpmAtom feed
Where each line stands
Plan an upgradeWhat to use instead
A better maintained package
From the e18e module-replacements list, maintained by the community.
The list compares the options for read-pkg: read the comparison.
Before you switch
- 1
Check what else depends on it
Paste your package.json in the dependency check to see every deprecated or outdated package in one pass, not only this one.
- 2
Read the replacement's peers and releases
A native API or a few lines of code need no release notes, but check the Node version your project runs on.
- 3
Know when it ships
Follow the new package on inlinr: its releases and advisories land in your feed, and the time spent on the migration branch shows on its page.
Latest releases
Notes older than 90 days are read on the Releases tab.
Dependency tracking · free for 3 projects
Know when your own dependencies move
read-pkg 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 3 Nov 2026. Releases and advisories last read 3 Nov 2026.