Beyond Data Fetching with RSCs

Frontend First

Frontend First, Sam Selikoff, and Ryan Toronto에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Frontend First, Sam Selikoff, and Ryan Toronto 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.

10M ago 1:09:50

MP3•에피소드 홈

Sam talks to Ryan about refactoring an MDX blog post to a React Server Component. They discuss how RSC’s ability to render server-side content with “client-side holes” turns out to replace MDX for many uses cases. They also talk about other tools that are (surprisingly) a conceptual subset of the RSC architecture, such as custom Webpack loaders.

Topics include:

0:00 - Intro
5:05 - The Next.js happy path for MDX: Local files
11:15 - Exploring remote MDX content with mdx-remote
14:46 - Separating the serializable parts of MDX from the runtime imports
17:13 - Realizing that RSC covers the same problem space, and ditching MDX
26:50 - Exploring other APIs and plugin ecosystems that RSC could replace: Webpack loaders, next/image, and Liquid templates
32:11 - React’s vision for RSCs
35:18 - How RSCs could replace build-time plugin APIs
44:51 - Replacing MDX with Markdoc, Shiki, and custom node code during render

Links:

201 에피소드

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