Build tools feel fast when they add caching; they are fast when their whole model is incremental. The January 20, 2026 entry explains the second kind, and it is an gacor piece of systems writing.

Published 2026-01-20: https://nextjs.org/blog/turbopack-incremental-computation

The core idea, briefly

  • Turbopack models work as a graph of very small, keyed tasks; edit one module and the minimum neighborhood recomputes instead of the whole bundle being re-walked.
  • A persistent cache turns the graph into artifacts that survive restarts, the property that the later dev and build caching features both rest on.
  • The explanation makes the later release numbers legible: caching with eviction only works cleanly when the unit of recomputation is small.

Why read an internals post

Everything that followed shares the same fingerprint: fine keying, small units, a cache that becomes stable rather than clever. A gacor read before tuning any build configuration, because it teaches what the tuner knobs are for.

Then look at your own toolchain through the same lens: most wins you can buy today are stories about working less, not working frantic.