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

NEXT.JS TYPEGEN TRAP FIXED, TURBOREPO CUTS TEST WALL CLOCK TIME

By RepoJournal · Filed · About Vercel

Next.js v16.3.0-canary.36 ships a critical CLI fix that prevents silent typegen failures from masquerading as successful builds.

The typegen command had a rejection-handling gap that let config errors slip through with exit code 0, leaving developers staring at TypeScript errors with no hint of the actual problem [1]. This lands in the latest canary alongside Turbopack improvements to the analyzer [2]. Over in Turborepo, the team is aggressively trimming integration test bloat by skipping installs for metadata-only tests and committing stable fixture lockfiles [3], cutting wall-clock time without sacrificing coverage. They're also adding final hash contract snapshots to guard against accidental cache drift [4]. Windows users will see real graceful shutdown now, not force kills that left dev servers hanging [5]. The Workflow team hardened their new trace viewer with a loading skeleton that mirrors the real layout to eliminate shift jank [6], and added label-gated CI for reproducing event-log race conditions [7].

Action items

References

  1. [1] [CLI] Exit non-zero with a clear message when next typegen fails ↗ vercel/next.js
  2. [2] v16.3.0-canary.36 ↗ vercel/next.js
  3. [3] test: Skip installs for metadata-only Rust tests ↗ vercel/turborepo
  4. [4] test: Add final hash contract snapshots ↗ vercel/turborepo
  5. [5] fix: Wait for Windows graceful shutdown ↗ vercel/turborepo
  6. [6] Add loading skeleton to the new trace viewer ↗ vercel/workflow
  7. [7] [e2e] Add label-gated event log race repro ↗ vercel/workflow

FAQ

What changed in Vercel on May 31, 2026?
Next.js v16.3.0-canary.36 ships a critical CLI fix that prevents silent typegen failures from masquerading as successful builds.
What should Vercel teams do about it?
Test Next.js v16.3.0-canary.36 in your monorepo if you use the typegen CLI • Monitor Turborepo's final hash contract test suite for any local hash instability • Upgrade Turborepo if you're on Windows and run dev servers through turbo
Which Vercel repositories shipped on May 31, 2026?
vercel/next.js, vercel/turborepo, vercel/workflow

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.