# Vercel — Inside Workflow DevKit: How framework integrations work

- Company: Vercel (vercel.com)
- Announced: 2025-12-09T13:00:00+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://vercel.com/blog/inside-workflow-devkit-how-framework-integrations-work
- Record: https://forck.live/items/20779-inside-workflow-devkit-how-framework-integrations-work
- Subject: v0 / AI SDK / AI Gateway

Vercel's post explains the two-phase pattern (build-time and runtime) behind the Workflow DevKit (WDK) framework integrations, which now support eight frameworks including SvelteKit, Astro, Express, and Hono, with TanStack Start and React Router in active development. The WDK uses an SWC compiler plugin to transform the same input file into three outputs (client, step, and workflow modes) and handles framework-specific request object conversion via injected helper functions.

## Evidence

Verbatim from https://vercel.com/blog/inside-workflow-devkit-how-framework-integrations-work:

> On the surface, integrating WDK with Next.js looks nothing like integrating it with Express or SvelteKit. They all have different bundlers, routing systems, and developer experiences. But at its core, every framework integration follows the same two-phase pattern.

---

Record: https://forck.live/items/20779-inside-workflow-devkit-how-framework-integrations-work
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md