The Wire · Showcase
MESSENGER ADAPTER SHIPS, WORKFLOW COLD-START FIX LANDS, NEXT.JS TURBOPACK GAINS ISOLATION
By RepoJournal · Filed · About Vercel
Meta Messenger is now a first-class chat platform with full webhook support and message caching [ref:1], while a critical workflow regression that broke deployments on cold starts is resolved [ref:6].
The chat SDK's new Messenger adapter [1] [2] brings HMAC-SHA256 webhook verification, generic and button templates, postback handling, and 98% test coverage—production-ready for conversational apps on Meta's network. Parallel shipping: button and modal callbacks now support webhook-based workflows via a new `callbackUrl` prop [3], letting you chain actions through external engines with server-side token storage. Over in workflow, a v2 regression where `world.js` got tree-shaken out of the bundle is now fixed [4]—first requests on cold starts no longer 500 with MODULE_NOT_FOUND. Next.js landed a crucial Turbopack feature: `chunkLoadingGlobal` config [10] lets you rename the global chunk variable from `TURBOPACK` to avoid conflicts when multiple Turbopack apps run on the same page (horizontal micro-frontends). The team also removed 22 ineffective turbo-tasks that were carrying more overhead than value [9], and fixed stale task rescheduling to respect invalidation priority [11]. Turborepo's VS Code extension now respects your theme colors instead of forcing gradients [5], and the LSP now correctly handles transit nodes and `$TURBO_EXTENDS$` sentinels [6] [7]. CLI logs command now gracefully handles non-READY deployments [8] instead of hanging.
Action items
- → Integrate Messenger adapter if you support multi-platform chat vercel/chat [plan]
- → Pull workflow v2 fix before your next deployment if using cold-start environments vercel/workflow [immediate]
- → Test chunkLoadingGlobal config if shipping micro-frontends on Turbopack vercel/next.js [plan]
- → Update VS Code extension and verify LSP diagnostics work correctly vercel/turborepo [monitor]
References
- [1] [messenger] add messenger (meta) platform adapter to chat sdk (#461) vercel/chat
- [2] [messenger] add messenger (meta) platform adapter to chat sdk ↗ vercel/chat
- [3] feat(chat): add callbackUrl to buttons and modals ↗ vercel/chat
- [4] fix(core): add world-init side-effect module to fix cold-start MODULE_NOT_FOUND ↗ vercel/workflow
- [5] fix: Remove VS Code task key gradient ↗ vercel/turborepo
- [6] fix: Allow transit nodes in LSP diagnostics ↗ vercel/turborepo
- [7] fix: Allow TURBO_EXTENDS in LSP diagnostics (#12770) vercel/turborepo
- [8] cli/logs: Handle non-live deployments ↗ vercel/vercel
- [9] Remove ineffective turbo-tasks (#91341) vercel/next.js
- [10] feat(turbopack): add chunkLoadingGlobal config option ↗ vercel/next.js
- [11] turbopack: reschedule stale tasks with correct invalidation priority ↗ vercel/next.js
FAQ
- What changed in Vercel on May 9, 2026?
- Meta Messenger is now a first-class chat platform with full webhook support and message caching , while a critical workflow regression that broke deployments on cold starts is resolved .
- What should Vercel teams do about it?
- Integrate Messenger adapter if you support multi-platform chat • Pull workflow v2 fix before your next deployment if using cold-start environments • Test chunkLoadingGlobal config if shipping micro-frontends on Turbopack
- Which Vercel repositories shipped on May 9, 2026?
- vercel/chat, vercel/workflow, vercel/turborepo, vercel/vercel, vercel/next.js