Advanced React State Boundaries in a Real Next.js App
Practical patterns for deciding what owns state across URL-reactive UI, browser-only APIs, RSC snapshots, TanStack Query, and optimistic updates.
Practical patterns for deciding what owns state across URL-reactive UI, browser-only APIs, RSC snapshots, TanStack Query, and optimistic updates.
In React, it’s always preferable to maintain a linear data flow. If a parent needs something, lift the state instead of smuggling it back up. All rules are made to be broken, though.
A practical guide to analyzing and reducing JavaScript bundle size. Learn bundle analysis, fix tree-shaking issues, remove duplicate libraries, and otherwise optimize your React app's JavaScript size.
There’s some very useful capabilities coming to JavaScript: “[Symbol.dispose]()” and “using”. Mat Marquis is here to explain why they’re coming and how to use them effectively.
Why slow React applications usually come from state placement, update scope, and architectural coupling - not missing memoization hooks.
Source maps are a vital part of modern web development, but a lack of standard has made it impossible for us to add new features or improve the debugging experience. This is the story of how we standardized source maps and how we continue to ship features through standards.
A deep dive into how React streams and renders UI out of order using Suspense boundaries
Learn about the most common data fetching patterns in React Server Components
A visual explainer by Sylvain Lesage on how HighTable works around browser scrollbar limits to display billions of rows, republished by Hyperparam.
Can React Server Actions replace fetch for client-side data fetching? Let's investigate and find out.
Aurora Scharff discusses React's async coordination primitives, and how React’s new era signals a fundamental shift in how devs build software.
Most HTML documents are relatively small, providing a starting point for other resources on the page to load. But why do some websites load several megabytes of HTML code? Usually it's not that there's a lot of content on the page, but rather that other types of resources are embedded within the do
This specification defines the QUERY method for HTTP. A QUERY requests that the request target process the enclosed content in a safe and idempotent manner and then respond with the result of that processing. This is similar to POST requests but can be automatically repeated or restarted without concern for partial state changes.