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 NUKES 327 INTEGRATION TESTS, CHAT SDK GAINS REAL SLACK EMULATOR, AI SDK BREAKS INSTRUCTION HANDLING

By RepoJournal · Filed · About Vercel

Next.js just migrated its entire legacy integration test suite to isolated tests and deleted 327 suites in one swing—the biggest test infrastructure shift in months—while chat and AI SDKs ship breaking changes that tighten their APIs.

The Next.js team completed a massive testing overhaul [1] [2], converting every test under `test/integration/` to run through `nextTestSetup` across `test/e2e/`, `test/production/`, `test/development/`, and `test/unit/`, then deleted the entire legacy folder. This isn't busywork—it's the foundation for faster CI and clearer test ownership. Separately, Next.js shipped `bfcacheId` [3] to let you opt out of state preservation when `cacheComponents` is enabled, giving control back to developers who need to reset UI state on navigation rather than preserve it. The chat SDK now handles Discord interactions properly in gateway-only mode [4], mapping slash commands and button interactions through the correct handler paths, and Telegram support for typed attachment uploads [5] rounds out multi-platform parity with `sendPhoto`, `sendAudio`, `sendVideo` methods. The AI SDK made instructions a core part of `prepareStep` [6] [7]—this breaks existing code because instructions now propagate across all future steps and properties like `content`, `files`, and `sources` accumulate rather than reset. Google Interactions API agents now support AbortSignal cancellation [8] so you're not left billing while a run spins. On the infrastructure side, NCC fixed extension resolution [9] to prioritize TypeScript over JSON files when both exist in the same directory—a quiet footgun that broke builds silently. Vercel CLI now injects `VERCEL_PROJECT_ID` and `VERCEL_ORG_ID` into `vercel dev` [10], matching production behavior so SDKs and telemetry work locally; there's also a fix for double-appended `rootDirectory` paths in per-directory-linked monorepos [11].

Action items

References

  1. [1] Convert test/integration to isolated tests (#93247) vercel/next.js
  2. [2] Convert test/integration to isolated tests ↗ vercel/next.js
  3. [3] bfcacheId: Opt out of state preservation (#93633) vercel/next.js
  4. [4] fix(discord): handle interactions in gateway-only mode ↗ vercel/chat
  5. [5] feat(telegram): support typed attachment uploads ↗ vercel/chat
  6. [6] feat: instructions as prepareStep input ↗ vercel/ai
  7. [7] fix(ai): accumulative properties on StreamTextResult, GenerateTextResult ↗ vercel/ai
  8. [8] feat(provider/google): support cancelling long-running Interactions API agents via AbortSignal, and process their intermittent stream ↗ vercel/ai
  9. [9] fix: Reorder extension resolution to prioritise TypeScript over JSON ↗ vercel/ncc
  10. [10] [cli] expose VERCEL_PROJECT_ID and VERCEL_ORG_ID to `vercel dev` process (#16282) vercel/vercel
  11. [11] [cli] fix `vercel dev` double-appending rootDirectory (#16279) vercel/vercel

FAQ

What changed in Vercel on May 12, 2026?
Next.js just migrated its entire legacy integration test suite to isolated tests and deleted 327 suites in one swing—the biggest test infrastructure shift in months—while chat and AI SDKs ship breaking changes that tighten their APIs.
What should Vercel teams do about it?
Audit vercel/ai usage of instructions and prepareStep—breaking change to instruction propagation [ref:11] • If you use Discord gateway-only mode, pull [ref:1] to restore interaction handling • Test `vercel dev` in per-directory-linked monorepos after [ref:21] to confirm rootDirectory paths
Which Vercel repositories shipped on May 12, 2026?
vercel/next.js, vercel/chat, vercel/ai, vercel/ncc, vercel/vercel

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.