Artwork

Content provided by Frontend First, Sam Selikoff, and Ryan Toronto. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Frontend First, Sam Selikoff, and Ryan Toronto or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ro.player.fm/legal.
Player FM - Aplicație Podcast
Treceți offline cu aplicația Player FM !

Implementing RSC, Part 1: Rendering

58:42
 
Distribuie
 

Manage episode 378310170 series 1635850
Content provided by Frontend First, Sam Selikoff, and Ryan Toronto. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Frontend First, Sam Selikoff, and Ryan Toronto or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ro.player.fm/legal.

Ryan shares how building his own RSC implementation from scratch helped him better understand React’s new paradigm. He and Sam talk about how a client React app can fetch an RSC Payload from a server endpoint to update the UI, how an RSC server renders and bundles Client code that’s part of a Server Component tree, and how a client-side Router can be used to fetch new RSC trees based on the URL.

Topics include:

  • 0:00 - Intro
  • 2:48 - Making a server endpoint that a client React app can use to re-render the UI
  • 15:42 - How the bundling step shims Client Components during a server render with a reference that the client app can later use to execute browser code
  • 35:16 - How the React Component API unifies server and client functionality in a single composable interface
  • 38:54 - How a client-side router can render different server trees based on the URL
  • 49:09 - Reference projects used

Links:

  continue reading

185 episoade

Artwork

Implementing RSC, Part 1: Rendering

Frontend First

198 subscribers

published

iconDistribuie
 
Manage episode 378310170 series 1635850
Content provided by Frontend First, Sam Selikoff, and Ryan Toronto. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Frontend First, Sam Selikoff, and Ryan Toronto or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ro.player.fm/legal.

Ryan shares how building his own RSC implementation from scratch helped him better understand React’s new paradigm. He and Sam talk about how a client React app can fetch an RSC Payload from a server endpoint to update the UI, how an RSC server renders and bundles Client code that’s part of a Server Component tree, and how a client-side Router can be used to fetch new RSC trees based on the URL.

Topics include:

  • 0:00 - Intro
  • 2:48 - Making a server endpoint that a client React app can use to re-render the UI
  • 15:42 - How the bundling step shims Client Components during a server render with a reference that the client app can later use to execute browser code
  • 35:16 - How the React Component API unifies server and client functionality in a single composable interface
  • 38:54 - How a client-side router can render different server trees based on the URL
  • 49:09 - Reference projects used

Links:

  continue reading

185 episoade

Toate episoadele

×
 
Loading …

Bun venit la Player FM!

Player FM scanează web-ul pentru podcast-uri de înaltă calitate pentru a vă putea bucura acum. Este cea mai bună aplicație pentru podcast și funcționează pe Android, iPhone și pe web. Înscrieți-vă pentru a sincroniza abonamentele pe toate dispozitivele.

 

Ghid rapid de referință