unstale

npm / @vercel/nft

@vercel/nft

What changed in @vercel/nft 0.30 to 1, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-26.

1 breaking1 new APIs and options5 behavior and defaults5 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.8 on npm

@vercel/nft 111 changes

Breaking changes 1

  • The package now requires Node.js 20 or newer, affecting which Node.js versions developers can use.

    1.0.0release notes

New APIs and options 1

Behavior and default changes 5

  • Adds catchall tracing for module-sync.

    1.10.0release notes

  • Traces pino transports in constructor and fastify patterns, helping include them in dependency tracing.

    1.5.0release notes

  • Tracing now includes pino transport target modules, so they can be included in traced output.

    1.4.0release notes

  • Supports module.createRequire when mixedModules is false, allowing dependency tracing in that configuration.

    1.2.0release notes

  • When tracing module-sync conditions, @vercel/nft also traces the cjs fallback.

    1.1.0release notes

Fixes and other changes 4

  • Package import wildcard trailers are now resolved.

    1.11.0release notes

  • Absolute paths outside the job base are no longer followed.

    1.3.2release notes

  • Symlinks are resolved relative to the real file location.

    1.3.1release notes

  • Nested export conditions are evaluated when resolving a module-sync fallback.

    1.1.1release notes

@vercel/nft 0.301 changes

Fixes and other changes 1

  • Reverts the change that emitted relative assets using cwd, restoring the prior behavior.

    0.30.3release notes