• React Digest
  • Posts
  • Notes on maintaining an internal React component library

Notes on maintaining an internal React component library

#361 – June 20, 2022


Check out the 5 different built-in views in the KendoReact Scheduler component (Day, Week, Month, Agenda and Timeline) as we go over common usage scenarios. See what flexibility you get in configuring this essential component.

this week's favorite

This document is a collection of my thoughts on maintaining a component library as part of an existing design system used by a large number of frontend applications. I don’t particularly care much for visual design—though I seem effective at implementing it—and am more interested in the software engineering and social challenges of building a large-scale component library.

React 18 was years in the making, and with it brought valuable lessons for the React team. Its release was the result of many years of research and exploring many paths. Some of those paths were successful; many more were dead-ends that led to new insights. One lesson we’ve learned is that it’s frustrating for the community to wait for new features without having insight into these paths that we’re exploring.

React Elements, Components, and Instances are different terms in React which work closely together. This guide will walk you through all three terms and explain them step by step. We will start off with the following code snippet as example.

Recently, while working with our large React app codebase, we came to a screeching halt against three categories of bugs — they were not compile-time or run-time errors but unexpected code behaviors.

Concurrent rendering addresses the performance problem with rendering large UI updates while keeping the UI responsive.