From 37b58f60bbfe7fd9dd235bc4d8a684088dc326d8 Mon Sep 17 00:00:00 2001 From: Tommy Chow Date: Tue, 9 Jun 2026 21:48:55 -0700 Subject: [PATCH] docs(web): correct Cache Components claim in AGENTS.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Feature is not enabled — no cacheComponents flag in next.config.ts and no 'use cache' directives in use. Clarify what's needed to opt in. Co-Authored-By: Claude Sonnet 4.6 --- web/AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/web/AGENTS.md b/web/AGENTS.md index 2421bdaf..7926777d 100644 --- a/web/AGENTS.md +++ b/web/AGENTS.md @@ -47,7 +47,7 @@ pnpm nuke # Delete .next, .open-next, node_modules, and pnpm-lock.yaml ## Cache Components -Enabled ([docs](https://nextjs.org/docs/app/getting-started/cache-components)) — everything is dynamic (SSR) by default. Opt into caching with `"use cache"` + `cacheLife()`, wrap async work in `` for PPR. Old `revalidate`/`dynamic`/`fetchCache` exports are replaced. Use `cacheTag()` + `revalidateTag()`/`updateTag()` for on-demand invalidation. Durable runtime cache requires R2 incremental cache (see `open-next.config.ts`) — without it, cache is in-memory only per Worker instance. +Not yet enabled — `cacheComponents` is not set in `next.config.ts` and no `"use cache"` directives are in use. Everything is dynamic (SSR) by default. To opt in: add `cacheComponents: true` to `next.config.ts`, use `"use cache"` + `cacheLife()` on server components/functions, and wrap async work in `` for PPR. Durable runtime cache requires R2 incremental cache (see `open-next.config.ts`) — without it, cache is in-memory only per Worker instance. ## Cloudflare Workers