Ensure unstable_cache bypasses for draft mode (#64007)
Currently we aren't detecting the draft mode case properly in `unstable_cache` so the cache is unexpectedly being leveraged. This ensures we bypass the cache for `unstable_cache` in draft mode the same way we do for the fetch cache handling. Fixes: https://github.com/vercel/next.js/issues/60445 Closes NEXT-2987
Showing
Please
register
or
sign in
to comment