Syntax - Tasty Web Development Treats 995: Next.js Vendor Lock-in No More
66 snips
Apr 13, 2026 Tim Neutkens, lead developer of Next.js who drives its architecture and features like the adapters API and TurboPack. He discusses making Next.js portable across platforms, the design and testing of the Adapters API, caching and cache synchronization strategies, runtime parity and debugging, and TurboPack’s design and incremental compilation approach.
AI Snips
Chapters
Transcript
Episode notes
Adapters API Unblocks Multi‑Platform Next.js
- The Adapters API creates a stable integration layer so Next.js can be hosted across providers and runtimes without fragile hacks.
- Tim Neutkens built it with partners like Cloudflare and Netlify and dogfooded it on Vercel first to avoid breaking customer sites.
Vercel Dogfooded The New Adapter Internally
- Next's new adapter was built from the ground up and dogfooded on Vercel to replace an older, battle-tested adapter.
- Tim describes the previous adapter dating back eight years and the careful rollout to avoid regressions on Vercel's large apps.
Build First Then Add Cache Components
- Optimize later: build your app first, then progressively add caching with cache components when you need performance gains.
- Use useCache and suspense boundaries to turn dynamic behavior into incremental optimizations rather than default complexity.