Packages

read-pkg-up

11.0.0 · 3 Nov 2023MIT40.6M / weekRepositoryHomepagenpmAtom feed

Deprecated by its maintainers: Renamed to read-package-upWhat to use instead

Upgrading read-pkg-up From 3.0.0 to 11.0.0

11 releases in betweennotes for 10

Reading releases, release notes and advisories…

4.0.0 has no release note on GitHub or in the repository's changelog, so its breaking changes are missing from the counts below.
  1. 3.0.0yours
  2. 4.0.0major
  3. 5.0.0major
  4. 6.0.0major
  5. 7.0.0major
  6. 1 release
  7. 8.0.0major
  8. 9.0.0major
  9. 1 release
  10. 10.0.0major
  11. 1 release
  12. 11.0.0target
10+
changes to make
0
advisories fixed
1+
new
?
fixes

Counted from 10 of 11 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

  1. 11.0.0

    Migration needed3 Nov 2023
    • Breaking

      Rename package from read-pkg-up to read-package-up 1e22fad

    • Breaking

      Require Node.js 18 935a546

  2. 10.1.0nothing new or fixed in the note

  3. 10.0.0

    Migration needed4 Jul 2023
    • Breaking

      Require Node.js 16 d027a92

  4. 9.1.0nothing new or fixed in the note

  5. 9.0.0

    Migration needed13 Oct 2021
    • Breaking

      Rename the readPackageUpAsync export to readPackageUp 8f870da

    • Breaking

      Require Node.js 12.20

  6. 8.0.0

    Migration needed28 Mar 2021
    • Breaking

      Require Node.js 12 e6fbe7f

    • Breaking

      This package now exports two named exports instead of a default export e6fbe7f

    • Breaking

      This package is now pure ESM. Please read this.

  7. 7.0.1nothing new or fixed in the note

  8. 7.0.0

    Migration needed27 Sep 2019
    • Breaking

      Rename .package to .packageJson 8140c73 I'm really sorry about the churn. It was brought to my attention that package is a reserved keyword, and it meant that the result could previously not be easily destructured.

2 other lines we could not sort, mostly version bumps
  • Accept URL as cwd (#19) 840607e

    9.1.0
  • Documentation fix d96ce60

    7.0.1

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.