@vercel/nft 1.11.0

Used to determine exactly which files (including `node_modules`) are necessary for the application runtime.

@vercel/nft@1.11.0 was published on 2026-08-18. Its manifest declares 12 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=20.

All @vercel/nft versions · Permanent reference to 1.11.0 · Latest release

Package specifications

Version1.11.0
License declarationMIT
Published2026-08-18T15:49:23.460Z
Node.js requirement>=20
Type declarationsBundled declarations
Runtime dependency count12
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size347.21 KiB
Published file count44
Package typeNot declared
ES module entryNot declared
Default entry./out/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies38
Repository starsUnknown
Repository forksUnknown

Install @vercel/nft 1.11.0

npm install @vercel/nft@1.11.0
pnpm add @vercel/nft@1.11.0
yarn add @vercel/nft@1.11.0

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

Evidence and freshness