React Digest
React Digest
#551 – April 05, 2026
stuff that everybody knows
How to be a web developer: Stuff Everybody Knows
4 minutes by Laurie Voss
Laurie's guide for junior web developers covers the broad, unspoken knowledge needed to work effectively on the web. It started as a talk given at coding bootcamps and grew into this website. He does not teach syntax or frameworks but instead maps out what there is to learn. Laurie's advice is meant to stay useful over time, no matter what tools or technologies you work with.
Still writing tests manually? Meticulous AI is here.
sponsored by Meticulous
Most teams are forced to make the tradeoff between better coverage and more maintenance effort. But top engineering teams like Notion, Dropbox, Wealthsimple and LaunchDarkly have discovered a new testing paradigm. Built by ex-Palantir engineers, Meticulous creates and maintains E2E UI tests that covers every edge case of your web app without any developer effort - making it the only tool to improve both product quality and dev velocity.
Making React ProseMirror really, really fast
14 minutes by Shane Friedman
Shane describes how React was integrated with ProseMirror and optimized for speed. He says that the main issue was too many re-renders causing lag in large documents. By memoizing components, avoiding changing props, and using stable references, the system reduced renders dramatically. This made the editor fast enough to handle very large texts smoothly.
Two React design choices developers don’t like—but can’t avoid
11 minutes by Ryan Carniato
Signals were supposed to fix two things developers hated about React - deferred state updates and manual dependency arrays. But building Solid 2.0 revealed those weren't bad design choices. They were real discoveries. Once async enters a reactive graph, you cannot let speculative writes reach the UI before values settle, and effects must declare all dependencies upfront before running. These rules apply to any UI system, not just React.
Error handling in Next.js with catchError
6 minutes by Aurora Scharff
If you’ve used react-error-boundary in the Next.js App Router, you’ve probably run into its limitations with Server Components. It catches errors it shouldn’t, and its recovery mechanism doesn’t re-fetch server data. unstable_catchError from next/error is a framework-aware alternative that handles both problems. In this post, Aurora walks through what breaks, the workaround she used before, and how catchError fixes it.
Why we rolled our own React server components framework
19 minutes by Josh Wilson
Josh explains why a team replaced a standard React framework with a small custom one using React Server Components. Their approach cut JavaScript and loading time significantly while simplifying development. He explores the pros and cons of frameworks, shows how modern tools make custom setups easier, and argues that building your own framework can be a good choice when existing ones don’t fit your needs.
And the most popular article from the last issue was: