Making Sense of React Server Components
This year, the React team unveiled something they've been quietly researching for years: an official way to run React components exclusively on the server. This is a significant paradigm shift, and it's caused a whole lot of confusion in the React community. In this tutorial, we'll explore this new world, and build an intuition for how it works, and how we can take advantage of it.
Introduction So, here's something that makes me feel old: React celebrated its 10th birthday this year! In the decade since React was first introduced to a bewildered dev community, it’s gone through several evolutions. The React team has not been shy when it comes to radical changes: if they discover a better solution to a problem, they'll run with it. A couple of months ago, the React team unveiled React Server Components, the latest paradigm shift. For the first time ever, React components can run exclusively on the server. There's been so much friggin’ confusion about this online. Lots of
saved by
related reading
- We migrated 50,000 lines of code to React Server Componentsmux.com
- Navigating the future of frontendfrontendmastery.com
- RSC From Scratch. Part 1: Server Components · reactwg server-components · Discussion #5github.com
- Server Components – Reactreact.dev
- React Foundations: Server and Client Components | Next.jsnextjs.org
- How Mozilla’s Rust dramatically improved our server-side performance | Figma Blogfigma.com
- Getting Started: Server and Client Components | Next.jsnextjs.org
- Building Bulletproof React Components - Shu Dingshud.in
- Redirecting to: /react/react-server-componentspatterns.dev
- Web Applications 101 - Robin Wieruchrobinwieruch.de
- The Two Reacts — overreactedoverreacted.io
- One Year with Next.js App Router — Why We're Moving Onpaperclover.net