This week's tooling story is less about individual releases and more about a theme: closing the gap between what your tools assume about your system and what your system actually is. Go's flight recorder stops guessing when to capture traces. infrawise stops letting Claude guess your schema. The verification-over-prompts argument stops pretending prompt quality is your bottleneck. Three different problem spaces, same underlying correction.
Next.js stabilizes prefetch exports, renames runtime options
Three discrete changes landed in Next.js this week. prefetch is now stable and exported from the public API—no more reaching into internals. force-runtime is renamed to allow-runtime, which is a clarification of intent rather than a behavior change: the old name implied you were demanding a runtime; the new name admits you're permitting one. Finally, Stream Cache Components no longer restart the dev server on cache miss, which removes a genuinely painful iteration loop.
The prefetch stabilization matters because the previous instability created real API churn for anyone building navigation-heavy apps. Renaming the runtime config key is a find-and-replace migration, not a rethink. The cache miss fix is automatic on upgrade—no configuration needed.
