What shipped in Vercel on August 28, 2026?

Next.js just made production bundles smaller by default, and it's live on canary today. In total, 69 commits, 71 pull requests, and 11 releases landed.

Who contributed to Vercel on August 28, 2026?

14 developers shipped this update, including Luke Sandberg, Will Binns-Smith, Tobias Koppers, Andrew Clark, amitvijapur, akkadaska, grootbro, and NathanColosimo, and 6 more.

What were the notable Vercel updates?

Turbopack: enable export mangling by default in production builds (#97676), Turbopack: mangle exported names for smaller bundle sizes (#97672), and Upgrade Turbopack to hashbrown 0.15 (#97808).

Aug 28, 2026

$ the-wire · showcase

Turbopack export mangling ships by default on canary

By RepoJournal · Filed 06:55 UTC on August 28, 2026 · About Vercel

14 people shipped this

Tobias Koppers @sokra 2 cited

VaguelySerious @VaguelySerious 2 cited

ai-sdk-factory[bot] @ai-sdk-factory[bot] 2 cited

Luke Sandberg @lukesandberg 1 cited

Will Binns-Smith @wbinnssmith 1 cited

pranaygp @pranaygp 1 cited

msullivan @msullivan 1 cited

Andrew Clark @acdlite

amitvijapur @amitvijapur

akkadaska @akkadaska

grootbro @grootbro

NathanColosimo @NathanColosimo

Felix Arntz @felixarntz

fantix @fantix

Next.js just made production bundles smaller by default, and it's live on canary today.

Vercel's flagship framework shipped the export mangling that shrinks bundle payloads, now enabled by default in production builds on canary [1], building on the opt-in flag `experimental.turbopackMangleExportNames` introduced yesterday [2]. Tobias Koppers landed both changes, and the result is a meaningful win for anyone shipping Turbopack builds. Meanwhile, the Turbopack dependency graph got leaner: a Hashbrown 0.15 and DashMap 7.0-rc2 upgrade removes a duplicate codegen path and trims what ships to users [3]. Dev startup also cleans up more aggressively, expanding Turbopack's removal of stale `.next` output to traces, logs, and anything else that can be recomputed from cache [4]. On the AI SDK, Bedrock citation-enabled streams now accept valid citation deltas instead of throwing `AI_TypeValidationError` [5], and a stalled Claude Code WebSocket no longer masks an underlying timeout with an uncaught error [6]. The workflow telemetry story: healthy runs now print nothing [7]. If your run's event payload vanishes, the runtime fails with `CORRUPTED_EVENT_LOG` instead of redelivering forever [8]. Git dependencies are getting cheaper: `asyncio.sleep` and friends are now possible thanks to `call_later`/`call_at` support in vercel-py's custom event loop [9]. One run re-read a missing payload 12 times before this fix landed [10], which is exactly the failure mode this kills.

Action items

→ Test your production builds with Turbopack on canary to measure bundle savings from export mangling vercel/next.js [plan]
→ Upgrade @vercel/ai to pick up the Bedrock citation fix before relying on citation streams vercel/ai [plan]
→ Monitor workflow runs for behavior change after silent healthy execution logging is removed vercel/workflow [monitor]

References

[1] Turbopack: enable export mangling by default in production builds (#97676) vercel/next.js
[2] Turbopack: mangle exported names for smaller bundle sizes (#97672) vercel/next.js
[3] Upgrade Turbopack to hashbrown 0.15 (#97808) vercel/next.js
[4] Expand Turbopack dev cleanup (#97833) vercel/next.js
[5] fix: accept valid citation deltas in Amazon Bedrock streams (#18250) vercel/ai
[6] fix: prevent uncaught Claude Code bridge WebSocket errors from masking startup timeouts (#19750) vercel/ai
[7] Stop logging on healthy workflow execution ↗ vercel/workflow
[8] [world-vercel] Fail the run on a lost event payload instead of retrying forever ↗ vercel/workflow
[9] workflow: implement call_later/call_at in custom event loop ↗ vercel/vercel-py
[10] [world-vercel] Fail the run on a lost event payload instead of retrying forever (#3742) vercel/workflow