The Wire · Showcase
VERCEL CUTS RUNTIME SIZE 5%, WORKFLOW FIXES REPLAY CORRUPTION, CHAT ADDS ADAPTER CATALOG
By RepoJournal · Filed · About Vercel
Turbopack drops 2KB of wasted WebAssembly helpers while Workflow patches a critical event-log replay bug that was surfacing as data corruption.
The Next.js team shipped two runtime optimizations that collectively trim 2KB (5% savings) from Turbopack's default bundle [1], removing dead WebAssembly and helper code that was always loaded but rarely used. Over on Vercel's CLI, three infrastructure moves landed: maxDuration bounds are now configurable via environment variable instead of hardcoded across validators [2], OIDC flag resolution got wired into the build pipeline [3], and Connex connectors can now be created manually without managed setup [4]. The Workflow team fixed a critical replay divergence where buffered hook payloads could race concurrent sleeps, causing event-log corruption and `CorruptedEventLogError` on replay [5]. They also patched two defense-in-depth issues: lazy stream key requests that failed during `Run.getReadable()` [6] and truncated ref responses that corrupted in-memory event logs [7]. Chat shipped an adapter catalog as a zero-dependency subpath with typed metadata, env specs, and peer dependency helpers for onboarding flows [8], and expanded Slack emulator test coverage to 0.6.0 APIs [9].
Action items
- → Deploy Workflow patches immediately if you're replaying against stored event logs vercel/workflow [immediate]
- → Update Next.js canary to pick up 5% runtime savings in Turbopack builds vercel/next.js [plan]
- → Set VERCEL_CLI_SKIP_MAX_DURATION_LIMIT=1 if you need function timeouts above 900 seconds vercel/vercel [monitor]
References
- [1] [turbopack] Remove WebAssembly helpers from the default runtime (#94373) vercel/next.js
- [2] feat(build-utils): gate client-side maxDuration upper bound behind env var (#16539) vercel/vercel
- [3] [cli] bump @vercel/prepare-flags-definitions ↗ vercel/vercel
- [4] Support non-managed Connex connector creation ↗ vercel/vercel
- [5] [core] Forward-port: preserve event-log order in hook-vs-sleep replay races (#2171) ↗ vercel/workflow
- [6] [codex] Handle lazy stream key request failures ↗ vercel/workflow
- [7] [world-vercel] Validate ref resolve responses before use ↗ vercel/workflow
- [8] Add chat adapters catalog ↗ vercel/chat
- [9] test(slack): expand emulator coverage for emulate.dev 0.6.0 APIs ↗ vercel/chat
FAQ
- What changed in Vercel on June 9, 2026?
- Turbopack drops 2KB of wasted WebAssembly helpers while Workflow patches a critical event-log replay bug that was surfacing as data corruption.
- What should Vercel teams do about it?
- Deploy Workflow patches immediately if you're replaying against stored event logs • Update Next.js canary to pick up 5% runtime savings in Turbopack builds • Set VERCEL_CLI_SKIP_MAX_DURATION_LIMIT=1 if you need function timeouts above 900 seconds
- Which Vercel repositories shipped on June 9, 2026?
- vercel/next.js, vercel/vercel, vercel/workflow, vercel/chat