RepoJournal
Vercel @vercel
125 wires and counting
$ status: archived — this briefing has stopped; the archive stays readable. browse live briefings →

$ status

wire 2026-05-11
stories 25
GitHub RSS Archive Reviews Topics

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

TURBOPACK TELEMETRY NOW SHIPPING, NODE LAMBDA STREAMING BUG SEALED

By RepoJournal · Filed · About Vercel · Composed from the cited sources · methodology

lukesandberg slmnsh bensabic
3 people shipped this
lukesandberg @lukesandberg 2 cited slmnsh @slmnsh 1 cited bensabic @bensabic 1 cited

Vercel's build system fixed a silent streaming flip that could break custom AWS handlers, while Turbopack finally starts reporting what it's actually building.

The @vercel/node builder [1] now gates response streaming centrally for AWS Lambda custom handlers, plugging a gap where frameworks like Redwood could inadvertently enable streaming without explicit opt-in. This ships across NestJS, Koa, and Hono [2][3][4]. On the Next.js front, Turbopack production builds now report feature-usage telemetry [5], fixing a correctness bug in how metrics were counted — critical for understanding what features teams actually depend on at scale. The turbo-tasks engine got a proof-of-concept memory eviction system [6] that transparently swaps tasks to disk after snapshots, though it's not production-ready yet. Meanwhile, the chat SDK tightened its adapter internals [7], protecting extension points while keeping runtime state private — better forward compatibility for custom implementations. Release automation improved too [8], decoupling docs deployments from every main commit so they only publish after changesets actually succeed.

Action items

References

  1. [1] @vercel/node@5.7.17 ↗ vercel/vercel
  2. [2] @vercel/nestjs@0.2.79 ↗ vercel/vercel
  3. [3] @vercel/koa@0.1.58 ↗ vercel/vercel
  4. [4] @vercel/hono@0.2.78 ↗ vercel/vercel
  5. [5] [turbopack] fix feature usage telemetry ↗ vercel/next.js
  6. [6] Proof of concept: task eviction after snapshot for turbo-tasks-backend ↗ vercel/next.js
  7. [7] feat: make adapter internals protected to enable subclassing ↗ vercel/chat
  8. [8] ci: promote release branch on successful publish ↗ vercel/chat

$ ls vercel/reviews/ # the step-back reads

the week in review Turborepo adds Go workspace graph, fixes hashing the month in review Workflow 4.8 overhauls delivery and sessions, Eve compacts traces, Turbopack cache defaults on
Topics: JavaScript Full archive → Weekly reviews →

Quick answers

What shipped in Vercel on May 11, 2026?
Vercel's build system fixed a silent streaming flip that could break custom AWS handlers, while Turbopack finally starts reporting what it's actually building. In total, 7 commits, 7 pull requests, and 11 releases landed.
Who contributed to Vercel on May 11, 2026?
3 developers shipped this update, including lukesandberg, slmnsh, and bensabic.
What were the notable Vercel updates?
@vercel/node@5.7.17, @vercel/nestjs@0.2.79, and @vercel/koa@0.1.58.
♥

$ log @vercel --recent

Turbopack GC gets a config key and the runtime sheds peer state 172 shipped xAI drops Chat Completions, eve breaks registry installs, Turbopack widens tree-shaking 155 shipped Next.js fixes cache warming env bug, eve gains audience hooks 167 shipped Turborepo patches Remix and Nuxt env hashing, shop ships Eve agent 10 shipped

$ log --all # elsewhere on the wire

@openclaw Cold-start Gateway diagnostics stop crying wolf, doctor repairs plugin drift Agentic Coding Cline desktop bundles shrink, goose unblocks its own clicks

$ ls showcases/

Rails Django Laravel Node.js Go Vue.js Kubernetes HashiCorp Arch Linux Linux Anthropic OpenAI

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.