- Every time I see a new release of @nextjs.org, my mind goes into panic mode: "What have they done now?" The half of the JavaScript world that relies on constant breaking change for job security has made life a living hell for the half that doesn't.
- Our latest release was a minor (v15.2) – there are no breaking changes until v16. We are focused on performance improvements, stability, and soon a simplified caching model.
- I appreciate the response! But the caching thing is my example: the existing solution is marked “depreciated”, the new one “not ready for production”. This makes sense for Vercel but leaves all of the Next users without a good way to cache.
- unstable_cache() was never stable, it was a temporary API added. There are many ways to do caching in your backend – you didn't explicitly have to use this. "use cache" won't be ready for production until stable. It's regardless of the platform you deploy to. You can still use Redis or lru-caches.Feb 28, 2025 21:23
