Take your React knowledge to the next level with advanced concepts, strategies, techniques, patterns and in-depth investigations.

This book is a must if:

• You've gone through the React docs, implemented a few simple apps, and now are wondering: “How can I progress to the next level?”
• You've been working with React for a few years and you're confident that you know it inside and out. This book might have a surprise or two for you .
• You want to become the go-to person for everything React performance and be the source of in-depth "how things actually work" knowledge in your team.

But why?

React docs are very good to start with React. Millions of books, courses, and blogs are out there aimed at beginners. But what to do after you've started successfully? Where to go if you want to understand how things work on a deeper level? What to read if you've been writing React for a while and beginner or even intermediate-level courses are not enough? There are not many resources available for this. This is the gap this book aims to fill.

What the book aims to provide is the knowledge that allows you to progress from "can implement a basic todo app" to "React guru in my team". It begins right away with investigating and fixing a performance bug. It digs deep into what re-renders are and how they affect performance. Walks you through how the reconciliation algorithm works, how to deal with closures in React, various composition patterns that can replace memoization, how memoization works, how to implement debouncing correctly, and much more.

The book is very structured. Each chapter is an independent story, investigation, or deep dive focusing on a single topic. However, they are not completely isolated: each chapter builds on the knowledge introduced in the previous chapters. Also, each chapter tries to introduce only the knowledge required to understand the discussed concept, no more. To make the reading easier and more focused.

If your knowledge already extends beyond the simple "todo" app, it's very likely that you'll know a lot of the concepts already. For this case, every chapter has a bullet-point list of things you can expect to learn from it at the beginning, and a "Key takeaways" section, with a very short bullet-point summary of the things introduced. Just skimming through these first will give you a good idea of what's inside.

You can read the book from cover to cover, and I tried to make sure you'll have fun doing that. Or just focus on things that matter to you the most and skim through the "Key takeaways" sections of the rest of the chapters.

I'm new to React. Is this book a good fit for me?

The book's target audience is people who are already familiar with React. Ideally, they have implemented an app or two and now want to progress to the next level. If you're a complete beginner, the book may not be the best fit. It starts with investigating a small performance problem right away and assumes that the reader can implement at least a simple "todo" app by themselves.

Table of Contents

Chapter 1. Intro to re-renders

Chapter 2. Elements, children as props, and re-renders

Chapter 3. Configuration concerns with elements as props

Chapter 4. Advanced configuration with render props

Chapter 5. Memoization with use Memo, use Callback and React. memo

Chapter 6. Deep dive into diffing and reconciliation

Chapter 7. Higher-order components in modern world

Chapter 8. React Context and performance

Chapter 9. Refs: from storing data to imperative API

Chapter 10. Closures in React

Chapter 11. Implementing advanced de bouncing and throttling with Refs

Chapter 12. Escaping Flickering UI with use layout Effect

Chapter 13. React portals and why do we need them

Chapter 14. Data fetching on the client and performance

Chapter 15. Data fetching and race conditions

Chapter 16. Universal error handling in React

About the author

Nadia Makarevich is a frontend architect, coder, writer, and educator.

She used to work at Atlassian, where she was exposed to completely different types of frontend development in various teams, including Atlaskit, Jira Navigation team, Jira Ops team, Jira Frontend Platform team. The last one was responsible for the architecture, builds, deploys, and best practices of the entire Jira frontend repository (millions of lines of code now!).

After the joys and challenges of working for big tech, she decided to gain a completely different perspective and joined a small startup as a Founding Engineer.

Over the past two years she's been writing a blog dedicated to advanced concepts for React developers and have spoken at conferences throughout the world, from Europe to Australia.