vercel/nft

Health v2 · maintenance only

Adoption not part of the score

1669 stars · 182 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Node File Trace (@vercel/nft) is a Node.js library that statically analyzes application entry files to determine exactly which files, node_modules packages, and assets are needed at runtime. It provides the tracing engine used by Vercel and @vercel/ncc to produce minimal file lists for deployment without bundling.

Use cases

• trace which node_modules files are actually required at runtime
• generate a minimal file list for deploying a Node.js app to AWS Lambda
• package a Node.js serverless function without bundling
• tree-shake node_modules without webpack
• statically analyze require and import statements in a Node.js codebase
• find all assets and binaries a Node.js application depends on
• reduce deployment size by excluding unnecessary files

When to choose

• You need to know the exact set of files required to run a Node.js application for deployment or packaging
• You want tree-shaking of node_modules without actually bundling or moving assets and binaries
• You need programmatic tracing with support for ESM exports/imports conditions, dynamic requires, and assets

When to avoid

• You want a single bundled output file - use a bundler like webpack, esbuild, or @vercel/ncc instead
• Your project is not JavaScript/Node.js based
• You rely heavily on runtime-constructed require paths that static analysis cannot resolve

Facets

library · maturity active

developer-tools parser build-tool developer-tools backend web-development serverless static-analysis dependency-tracing file-tracing tree-shaking node-modules module-resolution esm serverless-packaging vercel automation nodejs

Member repositories

For agents

markdown · JSON · MCP: product_card(name="vercel/nft")