✳flâneur — a map of the web's best reading

We migrated 50,000 lines of code to React Server Components

mux.com · 5,300 words · saved by 1 readers

React Server Components are a lot. We recently rethought our docs and rebranded Mux and, while we were at it, moved all of mux.com and docs.mux.com over to Server Components. So… believe me. I know. I also know that it’s possible and not that scary and probably worth it. Let me show you why by answering the following questions: Why do Server Components matter, and what are they good for? What are they not good for? How do you use them, how do you incrementally adopt them, and what kind of advanced patterns should you use to keep them under control? By the end of all this, you should have a pretty good idea of whether you should use React Server Components and how to use them effectively. One great way to understand React Server Components is to understand what problem they’re solving. So let’s start there. Long ago, in days of yore, we generated websites on servers using tech like PHP. This was great for fetching data by using secrets and doing CPU-heavy work on big computers so that c

Explore this link on the map →

saved by

related reading