read-pkg-up
11.0.0 · 3 Nov 2023MIT40.6M / weekRepositoryHomepagenpmAtom feed
Upgrading read-pkg-up From 1.0.0 to 11.0.0
14 releases in betweennotes for 10
Reading releases, release notes and advisories…
- 10+
- changes to make
- 0
- advisories fixed
- 1+
- new
- ?
- fixes
Counted from 10 of 14 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking11.0.0
- Breaking11.0.0
- Breaking10.0.0
- Breaking9.0.0
- Breaking9.0.0
- Breaking8.0.0
- Breaking8.0.0
- Breaking8.0.0
- Breaking7.0.0
- Breaking5.0.0
Release by release
- Breaking
Rename package from
read-pkg-uptoread-package-up1e22fad - Breaking
Require Node.js 18 935a546
- Breaking
10.1.0nothing new or fixed in the note
- Breaking
Require Node.js 16 d027a92
- Breaking
9.1.0nothing new or fixed in the note
- Breaking
Rename the
readPackageUpAsyncexport toreadPackageUp8f870da - Breaking
Require Node.js 12.20
- Breaking
7.0.1nothing new or fixed in the note
- Breaking
Rename
.packageto.packageJson8140c73 I'm really sorry about the churn. It was brought to my attention thatpackageis a reserved keyword, and it meant that the result could previously not be easily destructured.
- Breaking
2 other lines we could not sort, mostly version bumps
- 9.1.0
Accept
URLascwd(#19) 840607e - 7.0.1
Documentation fix d96ce60
2 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.