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 default file-system caching. The update allows developers to explicitly cache individual React components and functions with surgical precision, while Watt handles the complexity of distributed cache configuration automatically. Note that enabling component caching disables traditional ISR caching due to Next.js 16 architectural limitations.
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: