@trieb.work/nextjs-turbo-redis-cache 1.17.0 → 1.18.1

package/.github/workflows/release.yml

@@ -1,207 +0,0 @@
-name: Release
-
-on:
-  push:
-    branches:
-      - main
-      - beta
-      
-# Minimal permissions:
-#   contents:      semantic-release pushes the release commit + tag to the branch
-#   issues:        @semantic-release/github comments on referenced issues
-#   pull-requests: @semantic-release/github comments on referenced PRs
-#   id-token:      npm Trusted Publishing OIDC token exchange
-permissions:
-  contents: write
-  issues: write
-  pull-requests: write
-  id-token: write
-
-jobs:
-  release:
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Create GitHub App token
-        id: app-token
-        uses: actions/create-github-app-token@v1
-        with:
-          app-id: ${{ vars.RELEASE_APP_ID }}
-          private-key: ${{ secrets.RELEASE_APP_PRIVATE_KEY }}
-
-      - name: Checkout code
-        uses: actions/checkout@v6
-        with:
-          # Need full history so the post-release audit can diff against pre-release SHA.
-          fetch-depth: 0
-          token: ${{ steps.app-token.outputs.token }}
-
-      - name: Capture pre-release SHA
-        id: pre
-        run: echo "sha=$(git rev-parse HEAD)" >> "$GITHUB_OUTPUT"
-
-      - name: Install pnpm
-        run: corepack enable
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v6
-        with:
-          node-version: '22'
-          cache: 'pnpm'
-
-      - name: Install dependencies
-        # --ignore-scripts blocks lifecycle scripts (preinstall/install/postinstall/prepare)
-        # of all dependencies. This is the primary defence against supply-chain attacks
-        # injected via a compromised transitive dep's postinstall hook.
-        run: pnpm install --frozen-lockfile --ignore-scripts
-      - name: Verify the integrity of provenance attestations and registry signatures for installed dependencies
-        run: npm audit signatures
-
-      - name: Build project
-        run: pnpm build
-
-      - name: Verify working tree is clean before release
-        # If install/build silently modified tracked files, abort before semantic-release
-        # can include them in the release commit.
-        run: |
-          if [ -n "$(git status --porcelain)" ]; then
-            echo "::error::Working tree is dirty before semantic-release. Aborting."
-            git status --short
-            git diff --stat
-            exit 1
-          fi
-
-      - name: Run Semantic Release
-        env:
-          GITHUB_TOKEN: ${{ steps.app-token.outputs.token }} # GitHub App token (bypasses required_signatures ruleset)
-          NPM_CONFIG_PROVENANCE: 'true'
-        run: pnpm exec semantic-release
-
-      - name: Audit semantic-release commit — fail if files outside allowlist were touched
-        env:
-          PRE_SHA: ${{ steps.pre.outputs.sha }}
-        run: |
-          # Allowlist must mirror the `assets` array in release.config.cjs.
-          # Any file outside this list being modified by the release run is suspicious
-          # and blocks the npm publish step below.
-          ALLOWED="package.json pnpm-lock.yaml CHANGELOG.md"
-
-          if [ "$(git rev-parse HEAD)" = "$PRE_SHA" ]; then
-            echo "semantic-release made no commit; nothing to audit."
-            exit 0
-          fi
-
-          echo "Auditing commits ${PRE_SHA}..HEAD"
-          CHANGED=$(git diff --name-only "${PRE_SHA}..HEAD")
-          echo "Files changed:"
-          printf '%s\n' "$CHANGED"
-
-          UNEXPECTED=""
-          while IFS= read -r file; do
-            [ -z "$file" ] && continue
-            match=false
-            for allowed in $ALLOWED; do
-              if [ "$file" = "$allowed" ]; then
-                match=true
-                break
-              fi
-            done
-            [ "$match" = false ] && UNEXPECTED="${UNEXPECTED}\n  ${file}"
-          done <<< "$CHANGED"
-
-          if [ -n "$UNEXPECTED" ]; then
-            printf '::error::semantic-release touched files outside the allowlist:%b\n' "$UNEXPECTED"
-            echo "::error::This may indicate a compromised dependency. Aborting publish."
-            exit 1
-          fi
-
-          echo "All changed files are within the allowlist."
-
-      - name: Check if current version is already published
-        id: version-check
-        env:
-          NPM_PACKAGE_NAME: '@trieb.work/nextjs-turbo-redis-cache'
-        run: |
-          VERSION=$(node -p "require('./package.json').version")
-          echo "version=$VERSION" >> "$GITHUB_OUTPUT"
-          if npm view "$NPM_PACKAGE_NAME@$VERSION" version --registry https://registry.npmjs.org/ >/dev/null 2>&1; then
-            echo "should_publish=false" >> "$GITHUB_OUTPUT"
-          else
-            echo "should_publish=true" >> "$GITHUB_OUTPUT"
-          fi
-
-      - name: Exchange GitHub OIDC token for npm token
-        id: npm-oidc
-        env:
-          NPM_PACKAGE_NAME: '@trieb.work/nextjs-turbo-redis-cache'
-        run: |
-          node <<'NODE'
-          const fs = require('node:fs');
-
-          const pkg = process.env.NPM_PACKAGE_NAME;
-          const reqUrl = process.env.ACTIONS_ID_TOKEN_REQUEST_URL;
-          const reqToken = process.env.ACTIONS_ID_TOKEN_REQUEST_TOKEN;
-
-          if (!pkg || !reqUrl || !reqToken) {
-            console.error('Missing required env for OIDC token retrieval');
-            process.exit(1);
-          }
-
-          const audience = 'npm:registry.npmjs.org';
-          const url = reqUrl + (reqUrl.includes('?') ? '&' : '?') + 'audience=' + encodeURIComponent(audience);
-
-          (async () => {
-            const idRes = await fetch(url, { headers: { Authorization: 'Bearer ' + reqToken } });
-            if (!idRes.ok) {
-              console.error('Failed to fetch GitHub OIDC token:', idRes.status, await idRes.text());
-              process.exit(1);
-            }
-
-            const idBody = await idRes.json();
-            const idToken = idBody.value;
-
-            const exUrl =
-              'https://registry.npmjs.org/-/npm/v1/oidc/token/exchange/package/' + encodeURIComponent(pkg);
-            const exRes = await fetch(exUrl, {
-              method: 'POST',
-              headers: { Authorization: 'Bearer ' + idToken },
-            });
-
-            const exText = await exRes.text();
-            if (!exRes.ok) {
-              console.error('OIDC token exchange with npm failed:', exRes.status, exText);
-              process.exit(1);
-            }
-
-            const exBody = JSON.parse(exText);
-            const npmToken = exBody.token;
-            if (!npmToken) {
-              console.error('npm exchange response missing token');
-              process.exit(1);
-            }
-
-            fs.appendFileSync(process.env.GITHUB_OUTPUT, `node_auth_token=${npmToken}\n`);
-            const npmrcPath = `${process.env.RUNNER_TEMP}/npmrc`;
-            const npmrc = [
-              'registry=https://registry.npmjs.org/',
-              'always-auth=true',
-              '//registry.npmjs.org/:_authToken=' + npmToken,
-              '',
-            ].join('\n');
-            fs.writeFileSync(npmrcPath, npmrc, { encoding: 'utf8' });
-            fs.appendFileSync(process.env.GITHUB_OUTPUT, `npmrc_path=${npmrcPath}\n`);
-            console.log('OIDC token exchange with npm registry succeeded');
-          })().catch((e) => {
-            console.error(e);
-            process.exit(1);
-          });
-          NODE
-
-      - name: Publish to npm (Trusted Publishing)
-        if: steps.version-check.outputs.should_publish == 'true'
-        env:
-          NPM_CONFIG_PROVENANCE: 'true'
-          NPM_DIST_TAG: ${{ github.ref_name == 'beta' && 'beta' || 'latest' }}
-          NPM_CONFIG_USERCONFIG: ${{ steps.npm-oidc.outputs.npmrc_path }}
-        run: npm publish --provenance --access public --tag $NPM_DIST_TAG --registry https://registry.npmjs.org/
-

package/.prettierrc.json

@@ -1,6 +0,0 @@
-{
-  "semi": true,
-  "singleQuote": true,
-  "printWidth": 80,
-  "trailingComma": "all"
-}

package/.vscode/settings.json

@@ -1,10 +0,0 @@
-{
-  "cSpell.words": [
-    "EJSON",
-    "Keyevent",
-    "keyspace",
-    "postboned",
-    "REDISHOST",
-    "REDISPORT"
-  ]
-}

package/ARCHITECTURE.md

@@ -1,431 +0,0 @@
-# Architecture – Cache Handler Logic
-
-This document describes the internal architecture of the cache handler, focusing on the three core functions (`get`, `set`, `revalidateTag` / `updateTags`), the shared hash maps, and the supporting infrastructure (`SyncedMap`, `DeduplicatedRequestHandler`).
-
-Two handler implementations exist side by side:
-
-| Handler                    | Next.js API                                            | File                            |
-| -------------------------- | ------------------------------------------------------ | ------------------------------- |
-| **RedisStringsHandler**    | Legacy `cacheHandler` (Next.js 15)                     | `src/RedisStringsHandler.ts`    |
-| **CacheComponentsHandler** | `cacheHandlers.default` (Next.js 16+ Cache Components) | `src/CacheComponentsHandler.ts` |
-
-Both follow the same fundamental pattern – store serialized data in Redis strings, maintain two in-memory hash maps for tags, and synchronize those maps across instances – but differ in the data shapes they receive from Next.js and in some performance optimizations.
-
----
-
-## Table of Contents
-
-1. [High-Level Overview](#high-level-overview)
-2. [Shared Hash Maps & Why They Exist](#shared-hash-maps--why-they-exist)
-3. [SyncedMap – The Synchronization Primitive](#syncedmap--the-synchronization-primitive)
-4. [DeduplicatedRequestHandler](#deduplicatedrequesthandler)
-5. [Core Function: `get`](#core-function-get)
-6. [Core Function: `set`](#core-function-set)
-7. [Core Function: `revalidateTag` / `updateTags`](#core-function-revalidatetag--updatetags)
-8. [RedisStringsHandler vs CacheComponentsHandler](#redisstringshandler-vs-cachecomponentshandler)
-
----
-
-## High-Level Overview
-
-```mermaid
-flowchart TB
-    subgraph "Next.js Runtime"
-        NX["Next.js Page / Route / Fetch / 'use cache'"]
-    end
-
-    subgraph "Cache Handler Instance (per Node.js process)"
-        GET["get()"]
-        SET["set()"]
-        REV["revalidateTag() / updateTags()"]
-
-        subgraph "In-Memory Maps"
-            STM["sharedTagsMap\n(SyncedMap<string[]>)\ncacheKey → tags"]
-            RTM["revalidatedTagsMap\n(SyncedMap<number>)\ntag → timestamp"]
-            DEDUP["inMemoryDeduplicationCache\n(SyncedMap<Promise>)"]
-        end
-    end
-
-    subgraph "Redis"
-        RS["Redis Strings\n(cached page/fetch data)"]
-        RH1["Redis Hash\n__sharedTags__"]
-        RH2["Redis Hash\n__revalidated_tags__"]
-        PUBSUB["Pub/Sub Channels\n(sync messages)"]
-        KSN["Keyspace Notifications\n(expired / evicted)"]
-    end
-
-    NX -->|"get(key, ctx)"| GET
-    NX -->|"set(key, data, ctx)"| SET
-    NX -->|"revalidateTag(tags)"| REV
-
-    GET <-->|"GET key"| RS
-    SET -->|"SET key EX ttl"| RS
-    REV -->|"UNLINK keys"| RS
-
-    STM <-->|"HSET / HDEL / HSCAN"| RH1
-    RTM <-->|"HSET / HDEL / HSCAN"| RH2
-    STM <-->|"PUBLISH / SUBSCRIBE"| PUBSUB
-    RTM <-->|"PUBLISH / SUBSCRIBE"| PUBSUB
-    KSN -->|"evicted / expired"| STM
-```
-
----
-
-## Shared Hash Maps & Why They Exist
-
-### The Problem
-
-Next.js calls `revalidateTag("product")` with **only the tag name**. It does **not** provide the list of cache keys that belong to that tag.
-
-At the same time:
-
-- Redis strings (the actual cache entries) are keyed by a cache key (e.g. `/products/[id]`), not by tag.
-- Redis has no native secondary index that maps a tag to all keys that carry it.
-
-Without an additional data structure, the only way to find all keys for a tag would be a `KEYS *` or `SCAN` over the entire keyspace, parsing every entry – far too expensive at scale.
-
-### The Solution: Two SyncedMaps
-
-| Map                  | Key                             | Value                | Purpose                                                                                                                |
-| -------------------- | ------------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| `sharedTagsMap`      | cache key (e.g. `/products/42`) | `string[]` of tags   | Reverse index: given a tag, iterate this map to find all affected cache keys                                           |
-| `revalidatedTagsMap` | tag name (e.g. `product`)       | `number` (timestamp) | Tracks _when_ a tag was last revalidated, used for lazy invalidation of fetch entries (implicit tags / `_N_T_` prefix) |
-
-Both maps live **in-memory** in every Node.js process and are **synchronized across instances** through Redis Hash + Pub/Sub (see [SyncedMap](#syncedmap--the-synchronization-primitive)).
-
-```mermaid
-flowchart LR
-    subgraph "sharedTagsMap"
-        K1["/products/42"] -->|"tags"| V1["['product', '_N_T_/products']"]
-        K2["/products/99"] -->|"tags"| V2["['product', '_N_T_/products']"]
-        K3["/blog/hello"]  -->|"tags"| V3["['blog', '_N_T_/blog']"]
-    end
-
-    subgraph "revalidatedTagsMap"
-        T1["_N_T_/products"] -->|"timestamp"| TS1["1716123456789"]
-    end
-```
-
-When `revalidateTag("product")` is called, the handler iterates `sharedTagsMap` to find `/products/42` and `/products/99`, then batch-deletes them from Redis in a single `UNLINK` call.
-
----
-
-## SyncedMap – The Synchronization Primitive
-
-`SyncedMap<V>` (`src/SyncedMap.ts`) wraps a standard `Map<string, V>` and keeps it synchronized across all Node.js processes via three mechanisms:
-
-### 1. Redis Hash (persistent state)
-
-Every `set()` writes to both the local map **and** a Redis Hash (`HSET`). On startup, `initialSync()` uses `HSCAN` to load the full hash into memory. A periodic re-sync (default ~1 hour, jittered) guards against drift.
-
-### 2. Pub/Sub (real-time cross-instance sync)
-
-Every `set()` and `delete()` also publishes a message on a dedicated channel. All other instances subscribe and apply the change to their local map immediately. This avoids the need for polling.
-
-```mermaid
-sequenceDiagram
-    participant I1 as Instance 1
-    participant Redis as Redis
-    participant I2 as Instance 2
-
-    I1->>Redis: HSET __sharedTags__ "/p/42" '["product"]'
-    I1->>Redis: PUBLISH sync-channel {type:"insert", key:"/p/42", value:["product"]}
-    Redis-->>I2: message on sync-channel
-    I2->>I2: map.set("/p/42", ["product"])
-```
-
-### 3. Keyspace Notifications (eviction / expiry cleanup)
-
-When Redis evicts or expires a cache key, the corresponding entry must be removed from the `sharedTagsMap` as well – otherwise the map would grow indefinitely. `SyncedMap` subscribes to `__keyevent@<db>__:evicted` and `__keyevent@<db>__:expired` and automatically deletes matching entries.
-
-This requires Redis to be configured with `notify-keyspace-events Exe`.
-
-```mermaid
-flowchart LR
-    REDIS["Redis expires key\n/products/42"] -->|"keyevent notification"| SM["SyncedMap\ndeletes '/products/42'\nfrom local map + hash"]
-```
-
-### Why not store tags inside the Redis string value?
-
-The tag information _is_ stored inside the cached entry value as well. However, during `revalidateTag`, the handler must find _all_ keys that have a given tag without deserializing every cache entry. The in-memory `sharedTagsMap` enables O(n) iteration over a lightweight map instead of O(n) deserialization of potentially large page payloads.
-
----
-
-## DeduplicatedRequestHandler
-
-`DeduplicatedRequestHandler<T, K>` (`src/DeduplicatedRequestHandler.ts`) is a generic request deduplication + short-lived in-memory cache wrapper. It is used by **both** `RedisStringsHandler` and `CacheComponentsHandler`.
-
-### Motivation
-
-In a single Next.js request, the same cache key can be read multiple times (e.g. layout + page + multiple fetch calls referencing the same data). Without deduplication, each `get()` would issue a separate `Redis GET`. With deduplication:
-
-1. The first call creates the Redis request promise and stores it in the `inMemoryDeduplicationCache`.
-2. Subsequent calls for the same key within the caching window (default 10s) return the stored promise.
-3. After the caching timeout, the entry is evicted.
-
-### Seed on Set
-
-When `set()` stores a value in Redis, it also **seeds** the deduplication cache with the serialized value. This means an immediately following `get()` is served from memory without hitting Redis at all.
-
-```mermaid
-sequenceDiagram
-    participant NX as Next.js
-    participant H as Cache Handler (either)
-    participant DC as DeduplicationCache
-    participant R as Redis
-
-    NX->>H: get("key-A")
-    H->>DC: has("key-A")? No
-    H->>R: GET "prefix:key-A"
-    H->>DC: set("key-A", promise)
-    R-->>H: serialized value
-    H-->>NX: parsed CacheEntry
-
-    NX->>H: get("key-A") (same or different request within 10s)
-    H->>DC: has("key-A")? Yes
-    DC-->>H: cached promise
-    H-->>NX: structuredClone of result
-
-    Note over DC: After 10s timeout
-    DC->>DC: delete("key-A")
-```
-
-The `inMemoryDeduplicationCache` itself is a `SyncedMap` configured with `withoutRedisHashmap: true` and `withoutSetSync: true` – it only uses the Pub/Sub delete channel so that revalidations on other instances can evict stale entries.
-
----
-
-## Core Function: `get`
-
-### What Next.js Passes In
-
-**RedisStringsHandler:**
-
-```typescript
-get(key: string, ctx: {
-  kind: 'APP_ROUTE' | 'APP_PAGE' | 'FETCH';
-  tags?: string[];         // explicit tags (FETCH only)
-  softTags?: string[];     // implicit tags like _N_T_/path (FETCH only)
-  revalidate?: number;     // FETCH only
-  fetchUrl?: string;       // FETCH only
-  isFallback: boolean;
-})
-```
-
-**CacheComponentsHandler:**
-
-```typescript
-get(cacheKey: string, softTags: string[])
-```
-
-The Cache Components interface is simpler: it receives only the cache key and soft tags (implicit tags for lazy invalidation).
-
-### What `get` Does
-
-```mermaid
-flowchart TD
-    A["get(key, ctx)"] --> B["Redis GET prefix:key"]
-    B --> C{Result found?}
-    C -->|No| RN["Return null/undefined"]
-    C -->|Yes| D["JSON.parse result"]
-
-    D --> CC{CacheComponents?\nCheck expire}
-    CC -->|Expired| DEL1["UNLINK key\nDelete from sharedTagsMap\nReturn undefined"]
-    CC -->|Valid| E
-
-    D --> E["Check revalidatedTagsMap\nfor all tags + softTags"]
-    E --> F{Any tag revalidated\nafter entry.lastModified/timestamp?}
-    F -->|Yes| G["UNLINK key from Redis\nDelete from sharedTagsMap\nReturn null/undefined"]
-    F -->|No| H["Return cache entry"]
-
-    H --> H2["RedisStringsHandler:\nreturn { value, lastModified, tags }"]
-    H --> H3["CacheComponentsHandler:\nConvert base64 → Uint8Array → ReadableStream\nreturn { value, tags, stale, timestamp, expire, revalidate }"]
-```
-
-### Key Details
-
-1. **Timeout**: Every `Redis GET` uses `AbortSignal.timeout(getTimeoutMs)` (default 500ms). If Redis is slow, the handler returns `null` so the page can be server-rendered instead of waiting.
-
-2. **Deduplication** (both handlers): Before hitting Redis, the deduplication cache is checked for an existing in-flight or recently resolved promise for the same key. Enabled by default (`redisGetDeduplication: true`) with a 10s caching window (`inMemoryCachingTime: 10_000`).
-
-3. **Lazy tag invalidation**: Instead of eagerly deleting all fetch entries when a page tag is revalidated, the handler records the revalidation timestamp in `revalidatedTagsMap`. During `get`, it compares `lastModified` / `timestamp` against the max revalidation timestamp of all related tags. If the entry is stale, it is deleted and `null` is returned. This is necessary because `revalidateTag` for implicit tags (`_N_T_` prefix) does not know which fetch cache keys are affected.
-
-4. **Value transformation** (CacheComponentsHandler): The stored value is a base64-encoded string (from a `ReadableStream<Uint8Array>`). On read, it is decoded back to `Uint8Array` and wrapped in a new `ReadableStream`.
-
----
-
-## Core Function: `set`
-
-### What Next.js Passes In
-
-**RedisStringsHandler:**
-
-```typescript
-set(key: string, data: {
-  kind: 'APP_PAGE' | 'APP_ROUTE' | 'FETCH';
-  // APP_PAGE: { html, rscData, headers: { 'x-next-cache-tags', 'x-nextjs-stale-time' } }
-  // APP_ROUTE: { body, status, headers: { 'x-next-cache-tags', 'cache-control' } }
-  // FETCH: { data: { headers, body, status, url }, revalidate }
-}, ctx: {
-  tags?: string[];
-  revalidate?: number | false;
-  cacheControl?: { revalidate: number; expire: number };
-})
-```
-
-**CacheComponentsHandler:**
-
-```typescript
-set(cacheKey: string, pendingEntry: Promise<{
-  value: ReadableStream<Uint8Array>;
-  tags: string[];
-  stale: number;
-  timestamp: number;
-  expire: number;
-  revalidate: number;
-}>)
-```
-
-Note that the Cache Components handler receives a **Promise** of the entry – the value is not yet available when `set` is called.
-
-### What `set` Does
-
-```mermaid
-flowchart TD
-    A["set(key, data, ctx)"] --> B["Construct CacheEntry"]
-
-    B --> B2["RedisStringsHandler:\nExtract tags from headers (APP_PAGE/APP_ROUTE)\nMerge with ctx.tags\nWrap in { value: data, lastModified: Date.now(), tags }"]
-    B --> B3["CacheComponentsHandler:\nAwait pendingEntry promise\nTee the ReadableStream (don't mutate original)\nConvert stream → Uint8Array → base64 string"]
-
-    B2 --> C["JSON.stringify(cacheEntry)"]
-    B3 --> C
-
-    C --> D["Calculate TTL"]
-    D --> D2["RedisStringsHandler:\nestimateExpireAge(revalidate || defaultStaleAge)"]
-    D --> D3["CacheComponentsHandler:\nentry.expire (already in seconds)"]
-
-    D2 --> E["Redis SET prefix:key serialized EX ttl"]
-    D3 --> E
-
-    C --> SEED["Seed deduplication cache\n(if redisGetDeduplication enabled)"]
-
-    E --> F{Tags changed?}
-    F -->|"Yes (or new)"| G["sharedTagsMap.set(key, tags)\n→ HSET + PUBLISH"]
-    F -->|"No change"| H["Skip tag update"]
-
-    G --> I["Done"]
-    H --> I
-```
-
-### Key Details
-
-1. **Tag extraction** (RedisStringsHandler): For `APP_PAGE` and `APP_ROUTE`, tags are encoded in the `x-next-cache-tags` header as a comma-separated string. The handler splits this and merges with `ctx.tags`.
-
-2. **Tag deduplication**: Before writing to `sharedTagsMap`, both handlers check if the current tags are identical to the already stored tags. If so, the write is skipped to reduce Redis operations.
-
-3. **Dedup cache seeding** (both handlers): The serialized value is immediately seeded into the `DeduplicatedRequestHandler`, so a following `get()` for the same key can be served from memory.
-
-4. **Stream handling** (CacheComponentsHandler): The `ReadableStream` from Next.js is tee'd – one branch is consumed to produce the stored base64 value, while the original stream is left intact for Next.js to continue using.
-
-5. **Parallel operations**: The Redis `SET` and the `sharedTagsMap.set()` run concurrently via `Promise.all`.
-
----
-
-## Core Function: `revalidateTag` / `updateTags`
-
-### What Next.js Passes In
-
-**RedisStringsHandler:**
-
-```typescript
-revalidateTag(tagOrTags: string | string[])
-```
-
-**CacheComponentsHandler:**
-
-```typescript
-updateTags(tags: string[], durations?: { expire?: number })
-```
-
-In both cases, the handler receives **only tag names** – no cache keys.
-
-### What `revalidateTag` / `updateTags` Does
-
-```mermaid
-flowchart TD
-    A["revalidateTag(tags)"] --> B["Normalize tags to Set"]
-
-    B --> C["For implicit tags (_N_T_ prefix):\nMark in revalidatedTagsMap with Date.now()"]
-    C --> NOTE["This enables lazy invalidation\nof nested fetch entries on next get()"]
-
-    B --> D["Scan sharedTagsMap:\nFor each (key, storedTags):\n  if any storedTag ∈ tags → add key to keysToDelete"]
-
-    D --> E{keysToDelete empty?}
-    E -->|Yes| F["Return early"]
-    E -->|No| G["UNLINK all matching Redis keys\n(batch operation)"]
-
-    G --> H["Delete from sharedTagsMap\n→ HDEL + PUBLISH"]
-
-    G --> I["Delete from inMemoryDeduplicationCache\n(if redisGetDeduplication enabled)"]
-
-    H --> J["Done"]
-    I --> J
-```
-
-### Key Details
-
-1. **Implicit tags (`_N_T_` prefix)**: When Next.js calls `revalidatePath("/products")`, it internally translates this to `revalidateTag("_N_T_/products")`. The handler cannot know which _fetch_ cache keys are nested inside that page. Therefore, it only records the timestamp in `revalidatedTagsMap`. The actual cleanup happens lazily in `get()` when the fetch entry is next accessed.
-
-2. **Batch deletion**: All matching Redis keys are deleted in a single `UNLINK` call (non-blocking Redis delete), minimizing network round-trips.
-
-3. **Cross-instance propagation**: The `sharedTagsMap.delete()` publishes a Pub/Sub message, so all other instances immediately remove the deleted keys from their local maps as well.
-
-4. **Dedup cache cleanup** (both handlers): Revalidated keys are also removed from the `inMemoryDeduplicationCache` to prevent stale data from being served from memory.
-
----
-
-## RedisStringsHandler vs CacheComponentsHandler
-
-| Aspect                    | RedisStringsHandler                                                              | CacheComponentsHandler                                                          |
-| ------------------------- | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
-| **Next.js version**       | 15+ (legacy `cacheHandler`)                                                      | 16+ (`cacheHandlers.default`)                                                   |
-| **Cache kinds**           | `APP_PAGE`, `APP_ROUTE`, `FETCH`                                                 | Unified (all via `'use cache'`, `cacheTag`, `cacheLife`)                        |
-| **Value format**          | Arbitrary JSON (page HTML, RSC data, fetch response)                             | `ReadableStream<Uint8Array>` ↔ base64 string                                   |
-| **Entry shape**           | `{ value, lastModified, tags }`                                                  | `{ value, tags, stale, timestamp, expire, revalidate }`                         |
-| **set() receives**        | Resolved data                                                                    | `Promise<CacheComponentsEntry>` (may not yet be resolved)                       |
-| **TTL calculation**       | `estimateExpireAge(revalidate)` – configurable function                          | `entry.expire` – passed directly by Next.js                                     |
-| **Tag source in set**     | `x-next-cache-tags` header + `ctx.tags`                                          | `entry.tags`                                                                    |
-| **Request deduplication** | Yes (`DeduplicatedRequestHandler`, default on)                                   | Yes (`DeduplicatedRequestHandler`, default on)                                  |
-| **In-memory caching**     | Yes (configurable `inMemoryCachingTime`, default 10s)                            | Yes (configurable `inMemoryCachingTime`, default 10s)                           |
-| **Revalidation function** | `revalidateTag(tagOrTags)`                                                       | `updateTags(tags, durations?)`                                                  |
-| **Implicit tag handling** | Stores timestamp in `revalidatedTagsMap`, lazy check in `get()` for `FETCH` kind | Stores timestamp in `revalidatedTagsMap`, lazy check in `get()` for all entries |
-| **Singleton pattern**     | External (user wraps in `module.exports`)                                        | Built-in `getRedisCacheComponentsHandler()` singleton                           |
-| **Key prefix resolution** | `keyPrefix` option or `KEY_PREFIX` / `VERCEL_URL` env                            | `resolveKeyPrefix()` with BUILD_ID fallback                                     |
-
-### Shared Architecture
-
-Despite the API differences, the core invalidation architecture is identical:
-
-```mermaid
-flowchart LR
-    subgraph "Both Handlers"
-        direction TB
-        A["Redis Strings\n(actual cache data)"]
-        B["sharedTagsMap\n(key → tags)"]
-        C["revalidatedTagsMap\n(tag → timestamp)"]
-        D["inMemoryDeduplicationCache\n(key → Promise)"]
-    end
-
-    SET["set()"] --> A
-    SET --> B
-    SET -.->|"seed"| D
-    GET["get()"] --> D
-    GET -->|"on miss"| A
-    GET -.->|"check staleness"| C
-    REV["revalidateTag()\nupdateTags()"] --> C
-    REV -->|"find keys via"| B
-    REV -->|"UNLINK"| A
-    REV -->|"cleanup"| B
-    REV -->|"evict"| D
-```
-
-Both handlers rely on `SyncedMap` for cross-instance consistency of the tag maps and use the same pattern of "find affected keys via `sharedTagsMap` → batch delete from Redis → clean up maps". Both also use `DeduplicatedRequestHandler` (enabled by default) to reduce Redis load by deduplicating concurrent `get()` calls for the same key and seeding the cache on `set()`.