Packages

@vercel/nft

1.11.10 · 19 Nov 2026MIT15.5M / weekRepositoryHomepagenpmAtom feed

Upgrading @vercel/nft From 0.18.2 to 0.30.4

45 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 0.18.2Latest1.11.10
  1. 0.18.2yours
  2. 0.19.0major
  3. 1 release
  4. 0.20.0major
  5. 1 release
  6. 0.21.0major
  7. 0.22.0major
  8. 3 releases
  9. 0.23.0major
  10. 1 release
  11. 0.24.0major
  12. 4 releases
  13. 0.25.0major
  14. 0.26.0major
  15. 5 releases
  16. 0.27.0major
  17. 10 releases
  18. 0.28.0major
  19. 0.29.0major
  20. 4 releases
  21. 0.30.0major
  22. 3 releases
  23. 0.30.4target

Before you upgrade

Tick each one off as you go
  • Breaking0.26.0
  • Breaking0.24.0
  • Breaking0.22.0

Release by release

  1. 0.30.3 – 0.30.42 releases, nothing new or fixed in the notes

  2. 0.30.2

    26 Sep 20251 fix
    • Fixed

      Fs.readFile emit relative assets using cwd

  3. 0.30.1

    23 Aug 20251 new
    • New

      Add special case for ffmpeg-static

  4. 0.30.0

    23 Jul 20251 new
    • New

      Add support for module-sync export condition in Node.js 22+ (#534) (7e915aa), closes #531

  5. 0.29.4

    30 May 20251 fix
    • Fixed

      Remove rimraf dependency

  6. 0.29.3nothing new or fixed in the note

  7. 0.29.2

    20 Feb 20251 fix
    • Fixed

      Upgrade to glob 10

  8. 0.29.1

    27 Jan 20251 fix
    • Fixed

      Bump @mapbox/node-pre-gyp

2 other lines we could not sort, mostly version bumps
  • Revert "fs.readFile emit relative assets using cwd" (#547) (78b3823), closes vercel/nft#542

    0.30.3
  • Revert "fix: resolve cjs deps as cjs instead of esm (#362)"

    0.24.2

9 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.