Sébastien Rigaux

Tech watch

← All links

Cache Components

Next.js’s explicit component and data caching model, including lifetimes and invalidation.

Next.js visual showing the article title about improving navigation in v0.

To reduce loading skeletons in v0, the team combines Next.js Partial Prefetching with cache rules suited to public and personalized data. Playwright instant() tests check that priority content is ready at click time, and remain in the codebase as CI regression checks.

Prefetching also responds to user intent: in large grids, details load on hover, focus, or touch rather than for every visible card. That adjustment followed a 2.9× increase in prefetch requests. The overall comparison reports lower daily costs, while cautioning that the change cannot be attributed to this refactor alone.

Aurora Scharff

Dark Vercel Shop banner reading “Production-ready Shopify storefront on Next.js” beside a line drawing of a shoe.

Vercel Shop pairs a Next.js storefront with Shopify, which remains responsible for the catalog, payments, and checkout. Cache Components serve product data quickly, then stream personalized content; meanwhile, the cart updates before the server responds through an optimistic UI.

The template adds agent-facing options: an opt-in shopping assistant, skills for extending the store, and Markdown served through the Accept header. It offers a concrete starting point for these flows while keeping Shopify as the commerce engine.

Screenshot of the vinext 1.1.0 release page on GitHub

vinext 1.1.0, the Vite plugin reimplementing the Next.js API, brings many behaviors in line with Next.js, especially for the App Router (redirect handling, metadata, special errors) and cache management. This release introduces stale-while-revalidate for use cache, serving stale entries while regenerating them in the background, and fixes several cache and server-side rendering inconsistencies. A milestone for those seeking a deploy-anywhere alternative to Next.js.

github-actions

Next.js 16.4 announcement illustration with Next.js logo on dark background

Next.js 16.4 makes Cache Components the recommended approach, now enabled by default for new projects created with create-next-app. This model lets you declare cache behavior at the component level, with APIs to control static or dynamic rendering and fine-tune prefetching. The release also brings agent tooling for migration, Turbopack optimizations (cache size, HMR, smaller bundles), support for React 19.3, and several experimental features for build and development.

Next.js Team