The moment you arrived · Gauri

HomeWorkBlogResumeContact

GauriGauri

© 2026 GauriAhmedabad, GujaratUpdated November 2026
WorkWritingResumeContact
in𝕏
All postsnextjs.org

Next.js

Next.js 16.4: Cache Components are now the recommended default

With 16.4, Vercel recommends Cache Components for every Next.js app and plans to make them the default in Next.js 17. Here is what that means and how to switch.

Oct 2026·5 min read
Lines of colourful code on a dark screen
Photo: Mitchell Luo on Unsplash

The headline

Next.js 16.4 shipped on 6 October 2026 with a clear message: "we're excited to recommend Cache Components as the best choice for every Next.js app." New apps from create-next-app have them on by default, and the team says they will become the default in Next.js 17.

Cache Components arrived in Next.js 16 (October 2025) and replace the old implicit caching with an explicit model: nothing is cached unless you say so, using the use cache directive.

Turning it on

Two flags in next.config.ts, the same ones this portfolio runs on:

ts
import type { NextConfig } from "next";

const nextConfig: NextConfig = {
  cacheComponents: true,
  partialPrefetching: true,
};

export default nextConfig;

Caching a fetch

Mark a function as cacheable with use cache and set how long it lives with cacheLife. This is how the GitHub graph on my home page stays fresh without hitting GitHub on every visit:

ts
import { cacheLife } from "next/cache";

export async function getContributions() {
  "use cache";
  cacheLife("hours");

  const res = await fetch("https://github.com/users/HUNNEY1426/contributions");
  return parse(await res.text());
}

Also in 16.4

  • next upgrade --agent and experimental.agentUpgrade (default 'security') let a coding agent apply upgrades for you.
  • Agent Skills to help adopt Cache Components, and opt-in agent feedback reports.
  • Turbopack: a disk cache that uses 20–25% less space, lazy server HMR and smaller CSS Module class names in production.
  • React 19.3, plus an experimental Rust-based React Compiler.

Coming from Next.js 15?

Next.js 16 itself also made Turbopack the default bundler (2–5× faster production builds, according to the release post), renamed middleware.ts to proxy.ts, and raised the minimum Node.js version to 20.9.

Sources & further reading

  • Next.js 16.4 release post
  • Next.js 16 release post
NewerAI coding agents in late 2026: from one assistant to a teamOlder CSS that became Baseline in 2026, and what to use it for
Back to all postsDiscuss on email ↗