RepoJournal
Vercel

@vercel

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

Pick a date

  1. Tue 5 may
  2. Wed 6 may
  3. Thu 7 may
  4. Fri 8 may
  5. Sat 9 may
  6. Sun 10 may
  7. Mon 11 may
  8. Tue 12 may
  9. Wed 13 may
  10. Thu 14 may
  11. Fri 15 may
  12. Sat 16 may
  13. Sun 17 may
  14. Mon 18 may
  15. Tue 19 may
  16. Wed 20 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

TURBOPACK TELEMETRY NOW SHIPPING, NODE LAMBDA STREAMING BUG SEALED

By RepoJournal · Filed · About Vercel

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/[email protected] ↗ vercel/vercel
  2. [2] @vercel/[email protected] ↗ vercel/vercel
  3. [3] @vercel/[email protected] ↗ vercel/vercel
  4. [4] @vercel/[email protected] ↗ 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

FAQ

What changed 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.
What should Vercel teams do about it?
Update @vercel/node to 5.7.17 and dependent builders (NestJS, Koa, Hono) before next deploy • Monitor Turbopack telemetry in next canary for accuracy — first production signal • Review chat SDK adapter if you subclass for custom handlers — protected surface is now stable
Which Vercel repositories shipped on May 11, 2026?
vercel/vercel, vercel/next.js, vercel/chat

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.