RepoJournal
Vercel

@vercel

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

What actually shipped in Vercel, written up every day — commits, pull requests, releases, and security advisories.

One email a day. Unsubscribe in one click.

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

WORKFLOW BETA REGRESSION FIXED, BENCHMARKS NOW SHOW WHAT MATTERS

By RepoJournal · Filed · About Vercel

The hook.resume() breakdown that tanked [email protected] has regression coverage in place [ref:1], and your performance dashboards just got a major readability upgrade [ref:2].

Workflow's isolated route bundles were silently breaking sandbox callbacks with a dynamic module error [1]. The fix adds hard regression tests so this doesn't ship again. In parallel, the benchmark comment table dropped the noisy Avg column and renamed P10 to Best (warm-start floor), adding directional deltas across Best/P75/P90/P99 [2]. NestJS Vercel builds now emit their own Build Output since they can't ride the Nitro preset path that Express/Fastify/Hono use [3]. Over in AI, WorkflowAgent was dropping assistant narration between tool calls [4], and HarnessAgent streams weren't emitting the message-level start part [5]. [email protected] shipped with direct NextRequest support in flag() and evaluate() outside App Router [6]. Eve's extension capabilities are now individually versioned with explicit epoch tracking [7], dev snapshots handle physical node_modules correctly [8], and dynamic tools now route through proper auth context [9]. Next.js is consolidating test infrastructure to share a single browser across suites [10], renamed turbopackTreeShaking to turbopackModuleFragments to reduce confusion [11], and dropped outputHashSalt from experimental [12].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] test: regression coverage for hook.resume() from isolated route bundles (o2flow beta.26 incident) ↗ vercel/workflow
  2. [2] [ci] Benchmark comment: Best column + best/p75/p99 deltas (drop Avg/P10) ↗ vercel/workflow
  3. [3] [nest] Fix NestJS Vercel build output ↗ vercel/workflow
  4. [4] fix: WorkflowAgent loses assistant narration between tool-call steps (#17380) vercel/ai
  5. [5] fix (harness): emit message-level start part on HarnessAgent streams (#16717) vercel/ai
  6. [6] [email protected] vercel/flags
  7. [7] feat(eve): enforce extension capability compatibility ↗ vercel/eve
  8. [8] Fix dev snapshots for physical node_modules installs ↗ vercel/eve
  9. [9] fix(eve): dynamic tools - provide auth context ↗ vercel/eve
  10. [10] [ci] Share a single browser instance across all test suites in a single job ↗ vercel/next.js
  11. [11] [turbopack] Rename `turbopackTreeShaking` to `turbopackModuleFragments` ↗ vercel/next.js
  12. [12] Move outputHashSalt out of experimental ↗ vercel/next.js

Quick answers

What shipped in Vercel on July 21, 2026?
The hook.resume() breakdown that tanked [email protected] has regression coverage in place [ref:1], and your performance dashboards just got a major readability upgrade [ref:2]. In total, 66 commits, 71 pull requests, and 15 releases landed.
Who contributed to Vercel on July 21, 2026?
17 developers shipped this update, including pranaygp, VaguelySerious, molebox, Walter Korman, Lars Grammel, Don Neumark, AlbertGao, and github-actions[bot], and 9 more.
What were the notable Vercel updates?
test: regression coverage for hook.resume() from isolated route bundles (o2flow beta.26 incident), [ci] Benchmark comment: Best column + best/p75/p99 deltas (drop Avg/P10), and [nest] Fix NestJS Vercel build output.

More from @vercel

Daily updates, in your inbox

Follow Vercel

What actually shipped in Vercel, written up every day — commits, pull requests, releases, and security advisories.

or

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

Elsewhere on the wire

Want every project, not just this one?