How to find a Next.js memory leak in production

How to find a Next.js memory leak in production
9 minutes by Xabier Lameiro

Next.js versions 15.5 through 16.2 contain three documented memory leaks, all fixed in 16.3.0. Each leak has a distinct growth pattern: slow drift tied to unique URLs, traffic-proportional growth worsened by client disconnections, or stepwise increases from middleware timeouts. On serverless, the same problems often appear as 504 timeouts rather than crashes.

Cut AI Coding Token Costs by up to 36% with Sonar Vortex
sponsored by Sonar

Sonar Vortex operates inside your AI coding agent’s inner reasoning loop, supplying deep architectural context before code is written, then verifying the output in real time. In testing, software defects dropped by 92% and token consumption decreased. Build safer code while spending less on LLM calls.

Use client hints for server-side timezone rendering
5 minutes by Sergio Xalambrí

Showing dates in a user's timezone is tricky because the server doesn't know it on the first visit. The @epic-web/client-hints package solves this by detecting the timezone on the client, storing it in a cookie, and reloading once so the server can render dates correctly from then on. After that first visit, the cookie persists and no reload is needed. This same pattern works for other user preferences like color scheme or locale.

Reliable query prefetching with TanStack router
7 minutes by Dominic Dorfmeister

Fetching data only inside components often causes unnecessary delays and waterfall requests. Using route loaders to prefetch data earlier improves performance, but keeping the loader and component in sync is easy to get wrong. Storing shared query options in route context solves this by giving both the loader and component a single source of truth, preventing drift and redundant fetches.

How to build a cinematic home page with a video background
13 minutes by Mensur Duraković

The challenge was making a looping background video work behind real text and a newsletter form, not just as decoration. The article walks through the full process: locking a color palette, generating an abstract video loop with the right prompt, processing the file, building the component, and handling contrast, accessibility, and multi-tenant branding. The key lesson is to design the frame first, then fit the video into it.

Choosing a React PDF Engine
6 minutes by Kittisak Ma

PDFium and PDF.js are the two engines behind most React PDF viewers. PDFium matches Chrome's color rendering by default, while PDF.js can match it too, but only if you turn on hidden config options. PDF.js wins on bundle size, text search, and accessibility, since it builds a real text layer that PDFium lacks natively. Neither engine is clearly faster, so the right pick depends on your documents.

And the most popular article from the last issue was:

• Google's modern-web-guidance skill against a real React app