unstable_ meaning
Unanswered
Pink salmon posted this in #help-forum
Pink salmonOP
https://nextjs.org/docs/app/api-reference/functions/unstable_cache
I was always thinking that "unstable" means not production-ready and will cause weird issues in the production environment.
But I reread this again, and it seems like "unstable" means the API will change in the future.
So my question is, functionality-wise, is it really production-ready, meaning it will not cause runtime issues?
I was always thinking that "unstable" means not production-ready and will cause weird issues in the production environment.
But I reread this again, and it seems like "unstable" means the API will change in the future.
So my question is, functionality-wise, is it really production-ready, meaning it will not cause runtime issues?
3 Replies
@Pink salmon https://nextjs.org/docs/app/api-reference/functions/unstable_cache
I was always thinking that "unstable" means not production-ready and will cause weird issues in the production environment.
But I reread this again, and it seems like "unstable" means the API will change in the future.
So my question is, functionality-wise, is it really production-ready, meaning it will not cause runtime issues?
Me, along with many people, are using this
unstable_cache api in production and it is fairly stable. However, it is being deprecated in the favour of "use cache" directive which is still only present in canary builds and is highly experimentalPink salmonOP
Why not let them exist at the same time? The API of unstable_cache seems to have been a standard in most backend frameworks.
@Pink salmon Why not let them exist at the same time? The API of unstable_cache seems to have been a standard in most backend frameworks.
the API will continue to exist until many major versions down the road but they are now working on the new use cache directive which gives more control and flexibility