unstable_cache
Found in 1 package: next-js
next-js(8 releases)
v16.3.1This release includes several bug fixes and improvements for Turbopack, next/image, and various routing and caching mechanisms. It also includes backported fixes for stability and performance.
v16.3.0-canary.92BreakingThis release includes various bug fixes, performance improvements, and documentation updates. Notably, it enforces body size limits for Server Actions in the Edge runtime and preserves basePath in redirect destinations.
v16.3.0-canary.16This release introduces an enhancement to cache signal handling during foreground revalidation and fixes an issue with encoding non-ASCII characters in cache tags.
v16.0.0BreakingNext.js 16 introduces Turbopack as the default development engine, adds Model Context Protocol (MCP) support, and enforces asynchronous access to Dynamic APIs. It also transitions ESLint to Flat Config by default and increases the default image cache TTL.
v15.5.5This release focuses on backporting critical bug fixes for ISR revalidation and typed routes, while introducing a new experimental middleware body size limit and deprecating Runtime configuration.
v16.0.0-beta.0BreakingNext.js 16 beta introduces Turbopack as the default development bundler, enables router scroll optimizations by default, and adds a Model Context Protocol (MCP) server for enhanced devtools integration.
v15.6.0-canary.8BreakingThis release introduces a breaking change making Flat Config the default for the Next.js ESLint plugin and includes critical fixes for unstable_cache revalidation and Rspack regex handling.
v15.2.0-canary.6This release updates the React dependency to a newer experimental version and provides documentation clarifications for the unstable_cache function.
Track Symbol Changes
Use the Change8 MCP server or GitHub Action to get notified when unstable_cache changes.
Learn More