#508 – June 01, 2025
how many requests should be made when navigating
One roundtrip per navigation
26 minutes by Dan Abramov
Dan discusses how many HTTP requests should be made when navigating to a new page in web applications. He explores various approaches to data fetching, starting with traditional HTML sites and contrasting with client-side approaches that often require multiple requests. Dan also examines the trade-offs between colocation and performance, analyzing several patterns including REST APIs, component-based fetching, loaders, server functions, GraphQL fragments, and React Server Components.
Learn how to monetize your SaaS with Clerk Billing
sponsored by Clerk
Subscription plans boost SaaS revenue but are hard to build from scratch. Clerk Billing simplifies it—offering a polished UI and built-in tools to manage plans and gate premium features without custom logic. This article shows how Clerk Billing works and how to implement it in your app.
Building a hold to delete component
3 minutes by Emil Kowalski
Emil shares how to build a "hold to delete" button component with a gradual reveal transition. He details the process of creating the effect using CSS clip-path properties, positioning an overlay that reveals itself when the button is pressed and held.
Why React error boundaries aren't just try/catch for components
4 minutes by Kent C. Dodds
If you've ever asked this, you're not alone. Kent digs into why React error boundaries exist, how they work, and why they're not just a fancy try/catch block for your UI.
The visual editor for React
10 minutes by Puck Editor
Puck is a visual editor for React that allows developers to build and customize pages with a component-based approach. It includes a simple configuration system for defining components and rendering both editor and page views, with various starter recipes available for Next.js, Remix, and React Router applications.
The beauty of TanStack Router
11 minutes by Dominik Dorfmeister
TanStack Router stands out as a superior routing solution due to its type safety, fine-grained state subscriptions, and thoughtful developer experience. The router offers fully type-safe path parameters and links, integrated search parameter validation, and prevents unnecessary re-renders through selector-based subscriptions. It supports both code-based and file-based routing approaches while providing built-in Suspense support, making it an ideal companion to React Query for building modern web applications.
Tests are dead. Meticulous AI is here.
sponsored by Meticulous
Meticulous automatically creates and maintains an exhaustive e2e UI test suite that covers every corner of your application – with no developer intervention required whatsoever. Dropbox, Lattice, Bilt Rewards and hundreds of organisations rely on Meticulous for their frontend testing. It is built from the Chromium level up with a deterministic scheduling engine – making it the only testing tool that eliminates flakes.
And the most popular article from the last issue was: