Watt 3.18 adds support for Next.js 16's new 'use cache' directive, enabling component-level distributed caching through Redis/Valkey integration. This solves a critical challenge for self-hosted Next.js deployments by providing shared cache across multiple application instances, eliminating cache inconsistencies that occur with
Table of contents
Permalink The Self-Hosting Challenge: Why Distributed Caching MattersPermalink Understanding Next.js 16's use cache DirectivePermalink What is Watt?Permalink Enabling Component Caching in WattPermalink Important: ISR Cache BehaviorPermalink Why Redis/Valkey for Next.js Caching?Permalink Getting StartedPermalink Learn MoreSort: