Understanding Caching and Data Revalidation in Cloudflare Pages with KV Binding (__NEXT_ON_PAGES__KV_SUSPENSE_CACHE)

[2820402]

1. I am confused about how caching and data revalidation work in Cloudflare Pages when setting the binding of KV in Wrangler with __NEXT_ON_PAGES__KV_SUSPENSE_CACHE. Does it store the cache for fetch or full page?
2. How do you revalidate the cache in KV?
3. Do revalidatePath and revalidateTag work in API routes to revalidate the cache in KV?
4. If the cache is read from KV, can we set the cacheTtl value when reading from KV?
5. What type of revalidation is supported: time-based revalidation, on-demand revalidation with revalidatePath?