Target: vercel/next.js Issue: vercel/next.js#81161 PR: vercel/next.js#94735 Field Lab:...
Scarab patched Turbopack's watcher to stop treating cache/generated artifacts as source changes, eliminating spurious invalidation cycles that were spiking dev-server memory and CPU. Next.js developers now see faster iteration with lower local overhead.
This field test targeted a Next.js Turbopack development-server issue where memory and CPU usage could grow heavily during local development.
The reported issue shape was broad:
Turbopack dev server used high RAM and CPU
route compilation caused large CPU spikes
each route compilation appeared to add substantial memory
This field test was against Next.js. The issue was Next.js...
This field test was against Kubernetes. The issue was Kubernetes...
This field test was against TypeScript. The issue was TypeScript...
The first version of the patch treated the issue as a nearest-root problem. That was too broad. The...
This is the fifth field test in my Scarab Diagnostic Suite series, and it is the most significant one...
This field test was against React. The issue was React...
