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

VERCEL SHIPS VITEST ACROSS MONOREPO, CUTS CLI TEST TIME 60%

By RepoJournal · Filed · About Vercel

The Vercel monorepo ripped out Jest entirely and migrated to Vitest, shattering CLI unit test times from 22 minutes to 9 minutes by sharding into 7 parallel chunks.

This isn't a gradual migration — it's a wholesale replacement [1] that touches every test runner, TypeScript global, and CI discovery mechanism across the workspace. The test time collapse comes from a clever Windows-compatible sharding strategy [2] that routes test paths through environment variables instead of CLI arguments, bypassing cmd.exe's 8191-character limit that was crippling parallel execution. Meanwhile, the team is laying groundwork for continuous bleeding-edge deployments with canary snapshot releases [3] that auto-publish to npm whenever main merges, letting CLI users stay on the cutting edge without waiting for stable releases. On the CLI side, two quality-of-life wins landed: `--yes` now enables full browser recovery flows for coding agents like Claude Code and Cursor [4], and Firewall commands finally surfaced in help output [5] after living hidden for too long. Across the stack, Workflow's doing heavy lifting — auto-detecting when serverExternalPackages accidentally hide workflow code [6], shipping serializable AbortController/AbortSignal [7], and fixing `this` binding in nested arrow step functions [8]. Turbopack shrank its task tracker [10] and next.js killed off stale CI credentials in favor of a dedicated GitHub app [11][12]. Security fixes landed quietly but critically: Turborepo now blocks OTEL token injection to spoofed origins [13], filters microfrontend proxy env vars [15], and validates Host headers before routing [16].

Action items

References

  1. [1] Replace Jest with Vitest across workspace tests ↗ vercel/vercel
  2. [2] [ci] Shard vercel CLI unit tests into 7 chunks via VITEST_TEST_FILES ↗ vercel/vercel
  3. [3] Add canary snapshot releases (#16206) vercel/vercel
  4. [4] refactor(cli): let `--yes` enable connex token recovery in non-TTY (#16074) vercel/vercel
  5. [5] feat(cli): Add Vercel Firewall CLI commands to help (#16205) vercel/vercel
  6. [6] Auto-remove workflow packages from serverExternalPackages (#1481) vercel/workflow
  7. [7] feat: serializable AbortController/AbortSignal (#1301) vercel/workflow
  8. [8] [swc-plugin] Capture lexical `this` for nested arrow step functions (#1935) vercel/workflow
  9. [9] docs: split v4/v5 content trees and fix version switcher end-to-end (#1948) vercel/workflow
  10. [10] [turbopack] Simplify local task tracking (#93478) vercel/next.js
  11. [11] [ci] Move Turbopack, Rspack and font data workflows off of `RELEASE_BOT_GITHUB_TOKEN` ↗ vercel/next.js
  12. [12] [ci] Migrate React sync off of `RELEASE_BOT_GITHUB_TOKEN` ↗ vercel/next.js
  13. [13] fix: Prevent OTEL token injection to spoofed origins (#12727) vercel/turborepo
  14. [14] fix: Resolve TypeScript `.js` extension imports to `.ts` files in boundaries ↗ vercel/turborepo
  15. [15] fix: Filter microfrontend proxy environments ↗ vercel/turborepo
  16. [16] fix: Validate microfrontend proxy Host header ↗ vercel/turborepo

FAQ

What changed in Vercel on May 6, 2026?
The Vercel monorepo ripped out Jest entirely and migrated to Vitest, shattering CLI unit test times from 22 minutes to 9 minutes by sharding into 7 parallel chunks.
What should Vercel teams do about it?
Upgrade your test suite to Vitest if you haven't — this is the monorepo standard now [ref:1] • If you're using Turborepo with remote cache, pull the OTEL token injection fix immediately [ref:16] • Check that your tsconfig `paths` aliases work with TypeScript ESM in turbo boundaries [ref:17]
Which Vercel repositories shipped on May 6, 2026?
vercel/vercel, vercel/workflow, vercel/next.js, vercel/turborepo

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.