How we cut Next.js memory from 5GB to 1GB

#583 – November 15, 2026

the react-query timer holding every SSR request

How we cut Next.js memory from ~5GB to ~1GB
10 minutes by Rohit Kashyap

React-query v3 starts a timer for every query during server-side rendering. Node ties each request's context to that timer, keeping the entire request in memory until the timer fires, up to 5 minutes later. Setting cacheTime to Infinity on the server prevents the timer from starting, since the query client is thrown away after each render anyway. Memory dropped from 4.8 GiB to 1.2 GiB per pod after the fix.

Don’t sacrifice quality for speed (ElevenLabs definitely doesn’t).
sponsored by Meticulous

Agents are writing code faster than ever. They even review their own work. But who’s reviewing them? One does a passable job and ships a buggy fix, the next copies it. Bugs spread faster than anyone can catch them. Leadership at Dropbox, Notion & ElevenLabs refused to trade this quality for speed. With Meticulous, every change is exhaustively verified, with zero developer effort.

Six React chart libraries against hand-written SVG: What I found
9 minutes by Pavel Gusev

Pavel compares six popular React chart libraries with hand-written SVG to evaluate their performance, code size, and ease of use. Tests show that most perform similarly with typical charts, but differences become significant with large datasets. TanStack Charts requires the least code, while visx and hand-written SVG offer better performance and smaller bundles. The best choice depends on project needs and priorities.

Rebuilding the global town square from scratch
28 minutes by Yagiz Nizipli

X rebuilt its web app to serve people, search crawlers, and link preview bots from one server instead of three. On a slow connection, the first post now appears in under 3 seconds, down from over 22. A small team built the first version in under six months using AI coding agents. Traffic is moving from the old app one country at a time, with the full signed-in rollout underway now.

Writable derived state: Stop synchronizing state
5 minutes by Corbin Crutchley

Instead of syncing server data into local state with a useEffect, store user edits separately and fall back to server data only when local state is empty. A simple null check replaces the effect entirely. This keeps user changes safe during background refreshes, removes unnecessary code, and matches how the feature actually behaves.

The console framework
3 minutes by Text.js

Text.js is a framework that lets you build React apps that render inside the browser's console using console.log. It supports React 19 features like Suspense, server rendering, and an App Router with real routes and layouts. Output appears as styled text frames using browser DevTools formatting, and the same app also runs in terminals. It includes keyboard input, charts, tables, and even an AI coding tool built with it.

And the most popular article from the last issue was:

newsletters