Implements function-level caching with the "use cache" directive for RSC functions in @rangojs/router.
npx skills add https://github.com/rangojs/rango --skill use-cache-rangojs
Please help me install this Agent Skill. Skill: use-cache Source: https://github.com/rangojs/rango/tree/main/packages/rangojs-router/skills/use-cache Command: npx skills add https://github.com/rangojs/rango --skill use-cache-rangojs
"use cache" at file level or "use cache: <profile>" per function to cache return values, with named profiles (ttl, swr, tags, foregroundOnAction) defined in createRouter({ cacheProfiles }). - Request safety guards: cookies() and headers() throw inside cached functions to prevent cross-user data leaks, while tainted ctx objects are excluded from cache keys and route-identifying fields are folded in automatically. - Handle replay and inline server actions: ctx.use(Handle) side effects are captured on cache miss and replayed on hit, and inline "use server" actions embedded in cached components stay invocable with frozen closure values. - Use Case: Cache a database query like getProducts() with a short profile so repeated requests across routes reuse the result, while a mutation calls updateTag() to hard-purge the entry for read-your-own-writes consistency. ## Quick Start Add the "use cache" directive to my async data function and configure a named cache profile with ttl and swr in createRouter.High-intent search queries and answers about installing and using this skill.
Add the "use cache" directive at the top of the file or inside an individual async function, optionally with a named profile like "use cache: short". A Vite transform wraps the export with registerCachedFunction so its return value is memoized with TTL and stale-while-revalidate behavior.
"use cache" caches individual functions or components at runtime, while the cache() DSL caches an entire route segment subtree including children. Use "use cache" for granular data-fetch memoization and cache() when a whole rendered subtree should be stored.
Per-request values like cookies and headers are not part of the cache key, so reading them inside a cached function could serve one user's data to another. Extract the value before the cached function and pass it as an argument so it is included in the cache key.
No. Passing a cached function to middleware() throws at boot because middleware must run on every request, and using one as a Static() or Prerender() handler throws because build-time rendering already caches. Call the cached function inside the middleware or handler instead.
Tag entries via cache profiles or cacheTag(), then call updateTag(...tags) inside a server action for an awaitable hard purge with read-your-own-writes semantics. Use revalidateTag(...tags) for non-blocking background invalidation from route handlers or webhooks.
lespacemanCreate framework-agnostic route trees and routers with type-safe TanStack Router core.
lgerard314Coordinates TanStack Query cache updates with Next.js server actions and cross-tab messaging.
zacharyr0thConfigure Next.js rendering strategies for SSG, SSR, ISR, and CSR.
NodeSentinelEnable Partial Prerendering in Next.js routes with cache components.