995: Next.js Vendor Lock-in No More

Syntax

In this episode, Scott and Wes sit down with Tim Neutkens and Jimmi Lai from the Next.js team to dig into the new Adapters API, what it takes to run Next.js across platforms like Cloudflare and Netlify, and how caching and infrastructure choices affect performance. They also go deep on TurboPack’s internals, why Next.js doesn’t run on Vite, and the evolution of bundling in the framework.Show Notes00:00 Welcome to Syntax!01:14 Introduction to Next.js and the Adapter PlatformNext.js Across Platforms02:23 The Adapters API: Features and Community Needs04:46 Building and Testing the Adapters API07:37 Infrastructure Requirements for Next.js Apps11:38 Caching Strategies and Performance Optimization13:29 The Role of Cache Components in Next.js17:21 First Steps of Optimizations.19:48 Blessed Adapters and Community Contributions22:56 Future Directions and Runtime Support25:05 Challenges with Different Runtimes and Debugging26:45 Webpack vs. TurboPack: The Evolution of Next.js29:45 Why Not Run on Vite?32:47 Navigating Bundler Challenges36:59 Building TurboPack: Lessons Learned41:42 Incremental Compilation and PerformanceEpisode with ByteDance’s Zack Jackson43:50 Framework Comparisons and Performance Metrics46:42 Exploring Future Directions for TurboPack49:44 TurboPack’s Integration and API Development52:50 Standardization in Bundler Tools56:52 TurboPack’s Adoption and User Experience57:49 Sick Picks + Shameless PlugsSick PicksTim: Acquired PodcastJimmy: Hydrangea CoffeeShameless PlugsJimmy: nextjs-across-platformsHit us up on Socials!Syntax: X Instagram Tiktok LinkedIn ThreadsWes: X Instagram Tiktok LinkedIn ThreadsScott: X Instagram Tiktok LinkedIn ThreadsRandy: X Instagram YouTube Threads.

In this episode, Scott and Wes sit down with Tim Neutkens and Jimmi Lai from the Next.js team to dig into the new Adapters API, what it takes to run Next.js across platforms like Cloudflare and Netlify, and how caching and infrastructure choices affect performance. They also go deep on TurboPack’s internals, why Next.js doesn’t run on Vite, and the evolution of bundling in the framework.

Show Notes

  • 00:00 Welcome to Syntax!
  • 01:14 Introduction to Next.js and the Adapter Platform
  • 02:23 The Adapters API: Features and Community Needs
  • 04:46 Building and Testing the Adapters API
  • 07:37 Infrastructure Requirements for Next.js Apps
  • 11:38 Caching Strategies and Performance Optimization
  • 13:29 The Role of Cache Components in Next.js
  • 17:21 First Steps of Optimizations.
  • 19:48 Blessed Adapters and Community Contributions
  • 22:56 Future Directions and Runtime Support
  • 25:05 Challenges with Different Runtimes and Debugging
  • 26:45 Webpack vs. TurboPack: The Evolution of Next.js
  • 29:45 Why Not Run on Vite?
  • 32:47 Navigating Bundler Challenges
  • 36:59 Building TurboPack: Lessons Learned
  • 41:42 Incremental Compilation and Performance
  • 43:50 Framework Comparisons and Performance Metrics
  • 46:42 Exploring Future Directions for TurboPack
  • 49:44 TurboPack’s Integration and API Development
  • 52:50 Standardization in Bundler Tools
  • 56:52 TurboPack’s Adoption and User Experience
  • 57:49 Sick Picks + Shameless Plugs

Sick Picks

Shameless Plugs

Hit us up on Socials!

Syntax: X Instagram Tiktok LinkedIn Threads

Wes: X Instagram Tiktok LinkedIn Threads

Scott: X Instagram Tiktok LinkedIn Threads

Randy: X Instagram YouTube Threads

Audio Player

-
--:--
--:--