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

TURBOPACK SLASHES BUILD MEMORY OVERHEAD. NEXT.JS STREAMING GETS LEANER

By RepoJournal · Filed · About Vercel

Turbopack's serialization pipeline now drops data proactively during persistence, cutting memory consumption from 16.74 GB to 15.69 GB on canary builds.

The win comes from a fundamental rearchitecture of how Turbopack buffers data before writing to disk [1]. Because in-memory organization uses FxHash while disk output requires a different hash function and sorted order, the compiler was forced to hold everything in scratch buffers. Now it drops data as it flushes, treating persistence as a streaming operation instead of a batch job. Meanwhile, Next.js is simplifying its prerender pipeline [2] with a new chunk-callback pattern that eliminates redundant stream operations, making staged renders easier to implement without tee()ing streams twice. The App Router's route params also got smarter: IsRootLayout hints now generalize to IsRootLayoutOrAbove [3], letting the client correctly identify which params live above the topmost layout.tsx. On the Workflow side, hook conflict detection evolved from a boolean to a actionable handle [4] - getConflict() now returns the Run object that owns the token, not just a yes/no, so duplicate runs can inspect status, await results, or cancel competitors. Over in vercel/ai, the SDK removed deprecated experimental exports [5] as generateImage graduates from experimental to stable, and Fireworks now reports token usage in streaming responses [6]. Eve framework support shipped out of experimental [7], meaning teams can deploy Eve projects without the feature flag.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] [turbopack] Drop data while serializing in `next build` (#94561) vercel/next.js
  2. [2] refactor: process streaming prerenders more efficiently ↗ vercel/next.js
  3. [3] Generalize IsRootLayout prefetch hint to IsRootLayoutOrAbove ↗ vercel/next.js
  4. [4] Replace hook.hasConflict with hook.getConflict() returning the conflicting Run (#2373) vercel/workflow
  5. [5] fix: Remove deprecated experimental generateImage exports (#16017) vercel/ai
  6. [6] @ai-sdk/fireworks@2.0.56 ↗ vercel/ai
  7. [7] [@vercel/frameworks] graduate Eve from experimental frameworks (#16612) vercel/vercel

Quick answers

What shipped in Vercel on June 13, 2026?
Turbopack's serialization pipeline now drops data proactively during persistence, cutting memory consumption from 16.74 GB to 15.69 GB on canary builds. In total, 38 commits, 44 pull requests, and 19 releases landed.
Who contributed to Vercel on June 13, 2026?
2 developers shipped this update, including lubieowoce and acdlite.
What were the notable Vercel updates?
[turbopack] Drop data while serializing in `next build` (#94561), refactor: process streaming prerenders more efficiently, and Generalize IsRootLayout prefetch hint to IsRootLayoutOrAbove.

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?

We use privacy-friendly analytics (Google Analytics, IP-anonymized) to see which pages help readers. No ads, and we never sell your data. See our Privacy Policy.