Post

Instant Insights gives you options for how to make a navigation instant: β€’ Stream the data behind a <πš‚πšžπšœπš™πšŽπš—πšœπšŽ> boundary β€’ Cache the data with '𝚞𝚜𝚎 πšŒπšŠπšŒπš‘πšŽ' Or allow the navigation to Block with πšŽπš‘πš™πš˜πš›πš πšŒπš˜πš—πšœπš πš’πš—πšœπšπšŠπš—πš = πšπšŠπš•πšœπšŽ.

1 repost11 likes

To guarantee instant navigations, the client must immediately render something when a link is clicked. Previously, Next.js tried to solve this by prefetching every link, a flurry of requests as you scrolled. Many of you told us this looked ridiculous, and frankly, we agree.

So, we're borrowing a trick from single-page apps. Next.js now prefetches one reusable shell per route and caches it on the client, instead of a separate request per link. A click renders the prefetched shell instantly while the rest of the page streams in from the server.

Instant Navigations builds on Cache Components. To migrate an existing app, install our Skill: npx skills add vercel/next.js --skill next-cache-components-adoption Then ask your agent to adopt Cache Components using the Skill.