Request Caching, Revalidation & Deduplication in Next.js
Unanswered
West African Crocodile posted this in #help-forum
West African CrocodileOP
How can I cache a request's result across multiple pages in Next.js to ensure the data is fetched only once, shared across all instances where it's used, and updated both at a regular interval (revalidation time) and on-demand by revalidating its tag—so that all occurrences reflect the latest data?
11 Replies
@West African Crocodile How can I cache a request's result across multiple pages in Next.js to ensure the data is fetched only once, shared across all instances where it's used, and updated both at a regular interval (revalidation time) and on-demand by revalidating its tag—so that all occurrences reflect the latest data?
unstable_cache api but this api is now deprecated in favour of "use cache" but use cache is still experimental and doesn't work in non canary releases(iirc)@Yi Lon Ma `unstable_cache` api but this api is now deprecated in favour of `"use cache"` but use cache is still experimental and doesn't work in non canary releases(iirc)
Is it officially deprecated?:o Because it wasn’t even ever released as stable lol, and as for now I believe
unstable_cache is the only viable way to cache data until “use cache” comes.@LuisLl Is it officially deprecated?:o Because it wasn’t even ever *released* as stable lol, and as for now I believe `unstable_cache` is the only viable way to cache data until `“use cache”` comes.
yes it is officially deprecated and yea it was never released as stable but me along with many other people are using it in production and it is quite stable
Well not officially deprecated yet until
“use cache” reaches stability. Anyway, it works nicely👍@Yi Lon Ma `unstable_cache` api but this api is now deprecated in favour of `"use cache"` but use cache is still experimental and doesn't work in non canary releases(iirc)
West African CrocodileOP
What if I need to cache a request for a user across different pages, but the request requires a dynamic API, such as retrieving the token from their cookies? Would unstable_cache work in this case?
let me show you an example
this code links an item from my platform over to an issue in your linear workspace