Packages

@vercel/nft

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

Upgrading @vercel/nft From 0.27.4 to 1.11.10

39 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 0.27.4Newest 0.x0.30.4
  1. 0.27.4yours
  2. 6 releases
  3. 0.28.0major
  4. 0.29.0major
  5. 4 releases
  6. 0.30.0major
  7. 4 releases
  8. 1.0.0major
  9. 20 releases
  10. 1.11.10target

Before you upgrade

Tick each one off as you go
  • Breaking1.0.0
  • Breaking1.0.0

Release by release

  1. 1.11.10

    19 Nov 20261 fix
    • Fixed

      Resolve require() in ES modules with the require condition (#626) (648c381), closes #621

  2. 1.11.9

    19 Nov 20261 fix
    • Fixed

      Trace createRequire regardless of the import's local name (#618) (1ae6a56), closes #617

  3. 1.11.7

    17 Nov 20261 fix
  4. 1.11.6

    17 Nov 20261 fix
    • Fixed

      Trace dependencies of .cjs files found as assets

  5. 1.11.5

    16 Nov 20261 fix
    • Fixed

      Trace files referenced with import.meta.resolve()

  6. 1.11.4

    16 Nov 20261 fix
  7. 1.11.3

    16 Nov 20261 fix
    • Fixed

      Trace files referenced with import.meta.dirname and import.meta.filename (#628) (63980d8), closes #627

  8. 1.11.2

    13 Nov 20261 fix
    • Fixed

      deps: bump glob to ^14.0.6

1 other line we could not sort, mostly version bumps

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