Next.js 16 ships with a major cleanup: synchronous dynamic APIs are gone, params are promises, and the middleware concept has been renamed to proxy. Server components remain the default way to fetch data, and the new cache components make partial caching much more explicit and composable.
Next.js
What's new in Next.js 16 server components
July 2, 20266 min readRasel Hossain
Next.js
Quick answer
Next.js 16 server components guide by Rasel Hossain. Learn about async params, cache components, and the removal of sync dynamic APIs.
#Next.js#React
How to do it
- 1
Update Next.js
Run npm install next@latest to get Next.js 16.
- 2
Replace sync APIs
Replace any synchronous dynamic API calls with their async equivalents.
- 3
Migrate middleware
Rename your middleware file to proxy and update the export syntax.
- 4
Use cache components
Import and use the new cache components for explicit partial caching.
Frequently asked questions
What changed in Next.js 16 server components?
Synchronous dynamic APIs are removed, params are now promises, middleware is renamed to proxy, and new cache components provide explicit caching.
Do I need to rewrite my app for Next.js 16?
Most apps need minimal changes. The biggest updates are replacing sync dynamic API calls and updating middleware to the new proxy format.
More articles
Related reading from the same areas — practical notes on shipping software.
Liked the article?
Have a similar problem in your business? Let's talk about building the fix.
Start a project