#531 – November 09, 2025
URLs can hold filters, settings, and preferences without needing databases or cookies
Your URL is your state
13 minutes by Ahmad Alfy
Ahmad shares his thoughts on how powerful URLs can be for storing application state. URLs can hold filters, settings, and preferences without needing databases or cookies. They make apps shareable and bookmarkable while working with browser history. Many developers overlook URLs as state management tools, reaching for complex solutions when the web's oldest feature might work better.
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.
Quality assurance for i18n in React
4 minutes by Lingual
Maintaining accuracy and consistency in translation files is essential for reliable multilingual React apps. Using tools like i18n-check as part of your QA process helps teams catch issues early and deliver a better experience for all users.
Using atomic state to improve performance in nested component trees
7 minutes by Nathan Leung
Nathan shares a very brief overview of the difference between vanilla React Context-based state management and atomic state management, with an interactive demo based on real-world clinical trial data showing how you can use atomic state to keep your app responsive and performant.
Encapsulate state in component
6 minutes by David Johnston
Child components should handle their own state transitions instead of relying on parent components to manage loading, success, and error states. When parents control every piece of state through props, it forces developers to duplicate state management logic across the codebase.
Partial prerendering
10 minutes by Wyatt Johnson
Next.js introduced partial prerendering to solve a problem where developers had to choose between fast static pages or slower dynamic pages that can access user data. Partial prerendering lets you serve static page parts instantly while streaming dynamic content separately. Wyatt argues this approach significantly improves loading times by delivering content immediately from edge servers while fetching personalized data in parallel.
And the most popular article from the last issue was: