If you have worked with refs in React, you probably know they have always felt a bit different from the rest of the API. Useful, yes—but also slightly awkward. With React 19, that changes. Passing a ref to a child component is now much more natural because ref can be handled like a normal prop . That means less boilerplate, cleaner components, and a simpler mental model. If you want to try this yourself, the Passing Refs in React 19 challenge on our platform lets you practice exactly this pattern. But first, let's understand what refs are and why the old way was painful. How refs work (and why they were awkward) A ref is just a way to keep a direct reference to something rendered by React, usually a DOM element. You normally use refs when you need to do something imperative: focus an input, scroll an element into view, measure size or position, or trigger methods like opening a modal.…