React Digest
React Digest
#547 – March 08, 2026
memory leaks in modern frontend frameworks caused by missing cleanup of timers, event listeners, and subscriptions
Frontend memory leaks: Analysis and benchmark study
28 minutes by Ko-Hsin Liang
Ko-Hsin investigates memory leaks in modern frontend frameworks caused by missing cleanup of timers, event listeners, and subscriptions. He analyzed 500 public React, Vue, and Angular repositories using AST-based detectors and found 55,864 potential leak patterns, with 86% of projects affected. Controlled benchmarks simulating component lifecycle cycles show that missing cleanup retains about 8 KB of memory per cycle, while proper cleanup results in near-zero growth, demonstrating how small oversights can accumulate during long user sessions.
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.
Understanding why React fiber exists
10 minutes by Sanku
React used to render components using recursive function calls, which meant it couldn't stop once it started. Sanku points out that it blocked the browser from handling user input like typing or clicking, making apps feel slow. Fiber solves this by breaking rendering into small units of work stored as linked objects in memory. React processes a few at a time, then hands control back to the browser, keeping the interface responsive while heavy updates run in the background.
Building design components with action props using async React
11 minutes by Aurora Scharff
React Conf 2025 established the concept of Async React, introducing three layers: async design, async router, and async data. In this post, Aurora puts the design layer into practice by building two components from scratch, progressively improving the UX during async work while keeping optimistic updates and loading states internal so consumers stay simple.
Error rendering with RSC
13 minutes by Ryan Toronto
Ryan describes how React Server Components handle errors differently across three rendering environments. In the RSC environment, errors get serialized into the data stream rather than crashing the render. The SSR environment crashes on errors outside Suspense boundaries, but leaves suspended content in its fallback state. Only the browser can properly catch and display errors through Error Boundaries, so the main goal is getting errors there as fast as possible.
How toCreate a per-request database instance with middleware
3 minutes by Sergio Xalambrí
React Router middleware can manage database connections by running setup and teardown code around your loaders and actions. Sergio shows you how to create a database instance at the start of a request, store it in context, then close it in a finally block so cleanup always happens. You can also wrap requests in a transaction that rolls back automatically on failure. Adding the middleware to your root route gives every route database access without repeating code.
Lastly, React is now owned by the React Foundation: A new home for React hosted by the Linux Foundation.
And the most popular article from the last issue was: