Playing with Server Components in Vercel’s Edge Runtime

Frontend First

Contenu fourni par Frontend First, Sam Selikoff, and Ryan Toronto. Tout le contenu du podcast, y compris les épisodes, les graphiques et les descriptions de podcast, est téléchargé et fourni directement par Frontend First, Sam Selikoff, and Ryan Toronto ou son partenaire de plateforme de podcast. Si vous pensez que quelqu'un utilise votre œuvre protégée sans votre autorisation, vous pouvez suivre le processus décrit ici https://fr.player.fm/legal.

3+ y ago 51:28

MP3•Maison d'episode

Ryan tells Sam about some experiments he’s been running using Server Components in Vercel’s new edge runtime. He talks about how components that suspend in the node runtime cause the static build of your Next.js app to wait until they unsuspend, while components that suspend in the edge runtime stream back fallback responses as data is being fetched. Ryan also tells Sam about a blocking JS trick he learned to alter the initial render of your clientside app based on client-specific data, like whether their theme preference is dark or light mode.

Topics include:

0:00 - Intro
1:00 - Running synchronous JS before React’s initial render of build-time generated HTML
17:03 - Using getServerSideProps on the edge in Next.js for run-time generated HTML
32:15 - Behavior of Server Components that suspend in edge runtime vs. node runtime

Links:

201 episodes

#Technology #Web #Ember #Software #Development #Design #Web Development #Tech #Software Development #Frontend #Ryan Toronto #Sam Selikoff #JavaScript #Emberjs