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 CUTS MEMORY 50%, AI SDK GAINS WORKFLOW CONTEXT, TURBOREPO LOCKS DOWN CACHE

By RepoJournal · Filed · About Vercel

Next.js just halved JsValue's footprint across millions of analyzer instances, the AI SDK now threads context through multi-step workflows, and Turborepo is enforcing hard filesystem boundaries on cached outputs.

The memory win [1] lands as a trifecta of structural optimizations to JsValue — boxing RequireContextValue, flattening WellKnownFunctionKind variants, and refactoring the proc macro — that directly reduce peak memory and improve cache locality on the analyzer's hottest paths. This matters: large apps instantiate JsValue millions of times during analysis, so a 64→32 byte shrink compounds fast. In parallel, Next.js is stabilizing `unstable_io` [2] after shipping it canary-only, cleaning up the API surface before general availability. Over in the AI SDK, the `WorkflowAgent` now surfaces `runtimeContext` and `toolsContext` [3] — the same typed state APIs that `generateText` and `streamText` already expose — letting multi-step workflows share validated context across tool calls and agent steps. The same PR set also fixed `prepareStep` message overrides [4] to carry forward across steps instead of resetting, and Gemini multi-turn image edits [5] now preserve prior images in stateless mode instead of silently dropping them. On the infrastructure side, Turborepo is hardening cache restore boundaries [6] to prevent symlinks and output globs from escaping the repository root, while the VSCode extension [7] now starts its own daemon instead of relying on `turbo run` to do it. Bun lockfile pruning [8] and turbo.json decoration visitor depth [9] both got surgical fixes to handle edge cases.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] perf(ecmascript): shrink JsValue 64→32 bytes (#93106) vercel/next.js
  2. [2] Stabilize `unstable_io` (#93621) vercel/next.js
  3. [3] feat(workflow): add runtimeContext and toolsContext to WorkflowAgent ↗ vercel/ai
  4. [4] fix(ai): carry prepareStep message overrides forward across steps ↗ vercel/ai
  5. [5] fix(provider/google): fix lack of image consistency when using Interactions API in stateless mode (#15071) vercel/ai
  6. [6] fix: Enforce cache filesystem boundaries ↗ vercel/turborepo
  7. [7] fix: Start daemon for VSCode Extension from the extension itself ↗ vercel/turborepo
  8. [8] fix: Preserve Bun nested dependencies during prune ↗ vercel/turborepo
  9. [9] fix: Handle JSON decoration visitor depth ↗ vercel/turborepo

Quick answers

What shipped in Vercel on May 8, 2026?
Next.js just halved JsValue's footprint across millions of analyzer instances, the AI SDK now threads context through multi-step workflows, and Turborepo is enforcing hard filesystem boundaries on cached outputs. In total, 57 commits, 61 pull requests, and 18 releases landed.
Who contributed to Vercel on May 8, 2026?
3 developers shipped this update, including gr2m, lgrammel, and anthonyshew.
What were the notable Vercel updates?
perf(ecmascript): shrink JsValue 64→32 bytes (#93106), Stabilize `unstable_io` (#93621), and feat(workflow): add runtimeContext and toolsContext to WorkflowAgent.

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?