Bug after nextjs 16.3.0: getting infinite fetches for RSC calls after deploy

[gergokee]

Setup: redis sentinel in kubernetes cluster

Versions where i experienced the bug:
"@fortedigital/nextjs-cache-handler": "3.2.2",
"next": "16.3.0",
"redis": "6.2.0",

Root Cause:
In Next.js 16.3.0, /_tree segment prefetches require the TreePrefetch format (compact route tree structure). When segmentData is missing from the cache entry, the server falls back to returning the full rscData (InitialRSCPayload). The browser in 16.3.0 (no x-nextjs-postponed: 2) calls writeDynamicTreeResponseIntoCache expecting TreePrefetch format — fails to parse the full RSC — rejects the cache entry with a retry — loops forever.

This PR fixes it:
#237

[AyronK]

Solved in #237

[AyronK]

It's still an issue, I tried testing it with the example project and the bug is still around. I'll look at it.

[AyronK]

Fixed in 3.3.0.

Warning

Next.js 16.3.0 breaking change: Starting with Next.js 16.3.0, prefetch requests for the app router's route tree (/_tree) require per-segment RSC payloads (segmentData) to be present in the cache entry. Versions of this package prior to 3.3.0 did not populate segmentData when restoring the initial cache from disk (via registerInitialCache), which caused the Next.js 16.3.0+ client to receive an unparseable response for /_tree prefetch requests and retry indefinitely.