NestJS 12 Goes Full ESM, npm 12 Breaks Lifecycle Scripts, and a Startup Charges $10k to Delete AI Code
npm 12's silent suppression of lifecycle scripts will break CI pipelines and install hooks that teams rely on for post-install setup. NestJS 12's ESM-only shift forces the same module-system reckoning that has been rippling through the Node ecosystem, and the Rspack swap cuts build times for one of the most widely used backend frameworks.
NestJS 12 ships with a full ESM migration across all core packages, Rspack replacing Webpack in the CLI, and Vitest becoming the default test runner. The CLI now handles both CommonJS and ESM projects during the transition. Astro 7.1 lands with support for running multiple dev servers in parallel, a feature aimed squarely at AI agent workflows, alongside memory optimizations for content collections.
npm 12 arrives as a stable release with a hard break: lifecycle scripts no longer execute automatically. The npm team recommends upgrading to 11.18.0 first as a stepping stone. On the tooling side, TanStack released an npm download chart that visualizes package popularity trends over time, and Mozilla's web-ext hit 10.5 for cross-platform browser extension development.
A startup called Slopfix is charging $10,000 per week to delete AI-generated code. In one engagement, they cut a 100,000-line codebase down to 35,000 lines while preserving functionality — a blunt signal that the volume of AI-authored code now creates its own maintenance burden.
npm 12's lifecycle-script change is the kind of breaking shift that looks small in a changelog but will silently corrupt installs across thousands of projects that depend on postinstall hooks for native bindings or code generation.
NestJS adopting Rspack over Webpack is a milestone for Rust-based bundlers in the enterprise Node space — it signals that the performance argument has won even in conservative, long-cycle frameworks.
Slopfix's business model is less a gimmick and more a leading indicator: AI code generation has shifted the bottleneck from writing code to deleting the surplus it produces.