Faster repeat builds and lighter initial loading
The dashboard moved to stable Turbopack and a TypeScript 7 check while deferring expensive browser features until they are needed.
Mohith / 5 min read- Webpack baseline
- 21.9 s
- Cold Turbopack
- 46.5 s
- Repeat Turbopack
- 8.32 s
What changed
The dashboard now uses stable Next.js 16.3 Turbopack and runs the TypeScript 7 native compiler as an explicit build gate. Tooling that still needs the legacy compiler API stays behind a narrow TypeScript 6 compatibility seam.
Large optional browser features no longer enter the initial client graph before their surfaces are visible or interactive.
What we measured
The practical Webpack baseline completed in 21.9 seconds. A clean Turbopack build took 46.5 seconds, so the cold path regressed. The next Turbopack build completed in 8.32 seconds and improved the repeat workflow.
These are measurements from one documented checkout and environment. They are evidence for the build decision, not a universal benchmark for every machine or deployment.
What loads later
Below-fold animation, usage charts, and desktop smooth scrolling are deferred until their surfaces become visible or interactive. The change reduces unnecessary work in the initial browser graph without removing those capabilities.
What the numbers do not prove
Build duration is not page speed, Core Web Vitals, proof generation time, or hosted authentication latency. The measurements support a faster repeat development path while keeping the slower clean cold build visible in the result.