Hands On: How To Migrate To 16 and "Use Cache"
summary
Migrates a Next.js 15 app to Next.js 16 by enabling cache components in next.config, installing next@latest, removing route segment dynamic flags, and adding the use cache directive at the top of static page files so pages render at build time. Uses cacheLife with the minutes profile (stale ~5m, revalidate 1m, expire ~1h) for ISR behavior, splits blog results into a Suspense boundary so categories are static and posts remain dynamic, tags cache entries for revalidation, and demos using use cache remote (Vercel Data Cache/Redis) as an upstream shield succeed.
AI-written summary · about
chapters (13)
- 0:00Migrating to Next.js 16 and cache
- 2:36Setting up Next.js app
- 5:02Updating to Next.js 16 and cache
- 7:53Cache revalidation setup
- 9:40Migrating blog page to cache
- 13:34Finalizing migration steps
- 15:02Answering audience questions about caching
- 21:22Advanced useCache remote
- 23:08Partial pre-rendering demo
- 24:33React suspense dev tools
- 26:38Preparing hands-on exercise
- 27:43Caching quiz with prizes
- 36:30Closing remarks
related talks
15mDon't Go South With Next.js Caching – Supercharging Performance
10mGradual Migration Strategies for Next.js
16mHigh-speed personalization with Next.js
15mGetting Started with Next.js
30mWhen NOT to Use Next.js
10mTaking the Next step
45mNext js: Build a State of the Art E commerce in Fullstack React
20mLarge Scale Projects Challenges (NextJS - Contentful)