Remove unneeded node modules from production builds - build-time pruning

Remove unneeded node modules from production builds - build-time pruning targets a $3.0B = 1,000,000 developer organizations x $3,000 ACV. Rationale: there are roughly 1M organizations running Node.js workloads in production (npm and StackOverflow usage). A tooling SaaS priced at $3K ACV targets small-to-mid teams paying for CI-integrated optimizers. total addressable market with medium saturation and a year-over-year growth rate of 12% organic growth in dev tooling and serverless optimization demand.

Key trends driving demand: Serverless adoption -- increases sensitivity to cold starts and package size, making pruning valuable.; Shift to CI-driven immutable deployments -- makes build-time automation hooks a reliable integration point for pruning.; Developer focus on supply chain and SBOMs -- teams want deterministic inventories and explanations for what was removed.; Growth of native modules and prebuilt binaries (Prisma, SQLite, ffmpeg) -- raises frequency of large unused artifacts ending up in node_modules..