---
title: "@playstack/cache-next"
description: "Shared Next.js incremental caching, Cache Components, and signed on-demand revalidation over Playstack Cache."
tags: ["package","infrastructure","cache","nextjs","isr","revalidation","free"]
---

{/* package-access:start */}

> **Free.** MIT licensed. Check preview availability before installing. See [package access](/docs/packages#access-policy).

{/* package-access:end */}

`@playstack/cache-next` maps an application-owned `@playstack/cache` driver onto Next.js caching without importing framework internals.

{/* package-install:start */}

## Install

After confirming [preview access](/docs/packages#access-policy), install the package at your application's shared Playstack version:

```sh
npm install --save-exact @playstack/cache-next@0.1.0-beta.1
```

Check the peer requirements below before choosing a runtime or provider.

{/* package-install:end */}

## Choose the Next.js cache boundary

- `createNextIncrementalCacheHandler()` supports the stable singular `cacheHandler` used by ISR, fetch caching, and Pages/App Router output from Next 14.1 onward.
- `createNextCacheComponentHandler()` supports Next 16 `cacheHandlers`, streamed Cache Component values, and distributed soft-tag invalidation.
- `createNextRevalidationHandler()` verifies a timestamped HMAC before invoking injected path and tag revalidation functions in either router.

Incremental entries use Node structured-clone serialization so buffers, typed arrays, and maps are not forced through JSON. Applications own the handler file, cache policy, secrets, and deployment topology.

{/* package-reference:start */}

## API entry points and requirements

Reference snapshot: `@playstack/cache-next@0.1.0-beta.1`. Import only the entry point your runtime needs. Paths below are relative to the installed package; use **Go to Definition** in your editor to inspect exact parameters, return types and overloads. Do not import the declaration-file paths directly.

| Public entry point | Declaration file |
| --- | --- |
| `@playstack/cache-next` | `./dist/index.d.ts` |
| `@playstack/cache-next/package.json` | No TypeScript declaration (asset or metadata export). |

Node.js engine requirement: `>=20`. This is not a claim that every entry point works in browsers or Workers.

### Peer dependencies

Keep existing framework versions that satisfy these ranges. Install optional peers only when using the corresponding adapter. The package manager resolves ordinary dependencies separately.

| Peer | Compatible range | When needed |
| --- | --- | --- |
| `@playstack/cache` | `0.1.0-beta.1` | Required by the package. |
| `next` | `>=14.1.0 <17` | Required by the package. |

For a complete first program, start with [Getting started](/docs/getting-started). For API lookup and partial-example conventions, see [Reading the reference](/docs/packages#reading-the-reference). Provider failures, lifecycle requirements and application responsibilities remain described in the guide above; types alone do not establish production safety.

{/* package-reference:end */}