RepoJournal
Vercel

@vercel

Next.js + the Vercel platform - frontend infrastructure for the web

Keep up with Vercel in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

NEXT.JS PLUGS MEMORY LEAK IN EDGE RUNTIME, FIXES DEV OVERLAY ENCODING BUGS

By RepoJournal · Filed · About Vercel

A critical sandbox memory leak that causes step-like heap growth in self-hosted Next.js servers is patched, while dev overlay symbolication now correctly handles project paths with special characters.

Next.js shipped a fix for a heap growth bug in the Edge runtime sandbox where one-shot `setTimeout` calls tracked by `TimeoutsManager` are never released after firing, causing monotonic resource accumulation and eventual OOM in long-lived standalone servers [1]. The same build addresses two dev overlay breaks: Turbopack's source map symbolication now handles percent-encoded project paths correctly by properly normalizing encoding before comparing file URIs [2], and the dev validation worker reads chunk source maps from disk to correctly map dynamic imports and server component chunks that Node.js never loads into its isolate cache [3]. A related fix disables the dev validation worker entirely when using Webpack instead of Turbopack, since Webpack keeps source maps in the compiler rather than on disk [4]. On the tooling side, an internal skill was added to benchmark React and Next PRs in sandboxes, running interleaved comparisons against mergebase and caching reusable builds between test runs [5]. On the AI SDK front, five patch releases cascaded across Google Vertex, Anthropic, Anthropic AWS, and Amazon Bedrock to propagate an Anthropic fix that now correctly reports thinking tokens as reasoning token usage [6], while Bedrock also dropped tool `strict` and `output_config.format` parameters that Claude models reject [7].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] fix(sandbox): release one-shot timeout ids after they run ↗ vercel/next.js
  2. [2] Fix dev overlay symbolication for project paths needing percent-encoding ↗ vercel/next.js
  3. [3] Read chunk source maps from disk in the dev validation worker ↗ vercel/next.js
  4. [4] Run dev validation in process when using Webpack ↗ vercel/next.js
  5. [5] [internal] Add a skill for benching changes in a sandbox ↗ vercel/next.js
  6. [6] @ai-sdk/[email protected] vercel/ai
  7. [7] @ai-sdk/[email protected] vercel/ai

Quick answers

What shipped in Vercel on July 26, 2026?
A critical sandbox memory leak that causes step-like heap growth in self-hosted Next.js servers is patched, while dev overlay symbolication now correctly handles project paths with special characters. In total, 10 commits, 10 pull requests, and 11 releases landed.
Who contributed to Vercel on July 26, 2026?
4 developers shipped this update, including petehunt, gaearon, unstubbable, and github-actions[bot].
What were the notable Vercel updates?
fix(sandbox): release one-shot timeout ids after they run, Fix dev overlay symbolication for project paths needing percent-encoding, and Read chunk source maps from disk in the dev validation worker.

More from @vercel

Daily updates, in your inbox

Follow Vercel

Keep up with Vercel in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?