$ show vercel/ncc
ncc (Node.js Compiler Collection) is a CLI tool and programmatic library that compiles a Node.js module along with all its dependencies into a single file, similar to gcc for C. It uses Webpack internally with custom loaders for TypeScript, asset relocation, shebang handling, and more. The output can be minified, source-mapped, and optimized with V8 compile cache. It is designed for serverless environments and npm package publishing. The codebase is well-structured with a clear separation between CLI (src/cli.js) and core API (src/index.js). It includes extensive integration tests covering dozens of popular npm packages (Express, React, Apollo, etc.). While the core logic is tightly coupled to Webpack, several utility functions are independently reusable.
The LLM identified 4 files worth highlighting for reuse:
Walks up the directory tree from a given file path to find the nearest package.json and checks if it has `"type": "module"`. This is a standalone utility that can be extracted to determine if a file is in an ES module context, useful for any Node.js tool that needs to decide output format or behavior based on the package type.
Extracts the base package directory from a file path by locating the last `node_modules` segment and capturing the package name. This is a reusable function for any tool that needs to identify which npm package a file belongs to, without requiring a full dependency tree traversal.
A simple regular expression to match Unix shebang lines (`#!...`). This is a self-contained, copy-paste-ready utility for detecting or stripping shebangs in scripts, applicable to any Node.js project that processes executable files.
Computes a cache directory path using the XDG_CACHE_HOME environment variable (falling back to `~/.cache`) and a SHA-1 hash of the current working directory. This pattern for deterministic per-project cache locations is reusable in any CLI tool that needs persistent build caches.