Debugging Prefetch Behavior in the App Router
Reading the Network tab like a professional to figure out what the router is actually prefetching and when.
This is placeholder body copy. In a real post there would be an argument here, built one paragraph at a time, with the kind of small detours that make a technical essay feel like it was written by an actual human.
The repository this page lives in exists to demonstrate behavior of the Next.js router, so the content is intentionally boring. Any similarity to real insight is entirely coincidental, if occasionally welcome.
If you are reading this from a prefetch-triggered hover, congratulations, the link worked. If you are reading it after a full navigation, that also counts, and you have learned something about how caches behave under load.
More posts
Why Your Bundle Is Bigger Than You Think
Source-map explorer, import cost, and the day-to-day habits that keep JavaScript payloads honest.
A Practical Guide to Server Actions
Moving mutation logic into the server runtime without giving up end-to-end type safety or progressive enhancement.
From Pages to App Router: A Migration Story
Six months of incremental adoption, what surprised us, and what we would do differently the second time around.