995: Next.js Vendor Lock-in No More

Syntax - Tasty Web Development Treats

Wes Bos

Tech News, Technology, News

4.9 • 1.2K Ratings

🗓️ 13 April 2026

⏱️ 64 minutes

🔗️ Recording | iTunes | RSS

🧾️ Download transcript

Summary

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 Next.js Across Platforms 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 Episode with ByteDance’s Zack Jackson 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 Tim: Acquired Podcast Jimmy: Hydrangea Coffee Shameless Plugs Jimmy: nextjs-across-platforms 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

Transcript

Click on a timestamp to play from that location

0:00.0	Welcome to Syntax today. We have Tim and Jimmy on today. Tim is the, of course, the lead
0:05.4	dev of Next.js and Jimmy is the head of NextJS. And they're here to talk to us today about
0:11.4	some cool stuff that they're rolling out around their adapters platform, which is going to allow you
0:16.4	to host NextJS on different providers like Cloudflare and Netlify, as well as like different
0:21.7	run times as well, meaning like if you want to use Node or Bun or whatever, you can, you can do that.
0:27.4	Conversation takes a little bit to get warmed up, but trust me, it's going to be worth it because
0:30.8	these are some super smart guys and I actually really enjoy this conversation. We talk about
0:34.9	caching, Next.js performance. We talked about TurboPack and all the
0:39.3	turbopac internals and the whole process of building that. We of course ask them, why don't you
0:45.3	just use VET? Like everybody else is asking, and they had a really interesting answer to that
0:49.3	as well, which is maybe, maybe one day. And infrastructure, just like in general, like next
0:57.2	JS, of course, is code. But it's also, if you want it to run like Versel, it requires a whole
1:03.2	bunch of infrastructure. So we kind of go through that as well. Let's get into it.
1:14.4	So. into it. So the other day, you guys launched what the adapter platform.
1:19.1	Tell us about what that is.
1:20.5	Yeah.
1:20.9	So we launched the adapters like API as like stable, which has been like a long time coming.
1:28.1	As you said, we've been working on it for close to a year at this point.
1:33.3	And so the idea, right, is that we kind of, next just by itself, you know, it runs super well with like sort of next start.
1:43.3	You know, like on the simple sort of like VPS,
1:45.7	you can sort of like tap into like all capacities of Next.
1:49.7	But when it comes to kind of scaling it,
	...

Please login to see the full transcript.

Previous episode | Next episode

Disclaimer: The podcast and artwork embedded on this page are from Wes Bos, and are the property of its owner and not affiliated with or endorsed by Tapesearch.

Generated transcripts are the property of Wes Bos and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.