995: Next.js Vendor Lock-in No More

The episode kicks off with an introduction to Next.js and its new adapters platform, which allows Next.js applications to be hosted on various providers like Cloudflare and Netlify and on different runtimes such as Node or Bun. The hosts highlight the need for this platform to improve scalability and infrastructure flexibility, moving beyond traditional hosting methods.

Tim and Jimmy discuss the development of the stable Adapters API, which aims to provide a consistent contract for hosting Next.js on multiple platforms. They detail their extensive testing process, including real-world deployment on their own applications, to ensure robustness. The importance of infrastructure — such as CDN proximity and database placement — for Next.js performance is emphasized, along with caching strategies to optimize response times and synchronization across servers.

The conversation shifts to caching approaches within Next.js, especially cache components that allow multi-layered caching — on the client, server, build time, and CDN. The hosts talk about how these strategies enable building highly performant, scalable applications and the ongoing efforts to support offline caching and synchronization. They explain how developers can progressively adopt caching features, starting simple and optimizing over time.

Tim and Jimmy explore the reasons behind Next.js’s reliance on TurboPack over Webpack or Vite. They discuss the challenges with traditional bundlers, especially related to incremental compilation and large codebases, and how TurboPack was designed to handle these issues with features like parallelization, incremental builds, and support for complex real-world edge cases. The future direction includes expanding runtime support and improving developer debugging experiences, aiming for a unified API that works across platforms.

The hosts analyze the potential for standardizing APIs for bundler plugins and runtime behaviors across different tools and platforms. They emphasize the importance of careful API design to avoid slowdowns and bottlenecks. Discussions include ongoing efforts to support newer runtimes like Bun and Cloudflare Workers, as well as research into making Next.js compatible with AI-driven development and debugging tools.

Sandwiched between deep technical discussions, there is a focus on community engagement through testing and contributions such as implementing Webpack-like APIs. They share insights on TurboPack's internal lessons, such as dealing with large-scale projects and complex edge cases, and how these learnings shape the future of Next.js's toolset. The importance of maintaining extensive, real-world tested features without sacrificing speed or developer experience is highlighted.