Workflow SDK's native Nitro v3 integration is now in beta. Steps run inside the same bundled runtime as the rest of your app, eliminating the separate bundle overhead. Nitro server-side APIs including useStorage() work directly inside "use step" functions.
Workflow routes are bundled by Nitro as part of the standard app build. Dependencies are traced, unused code is tree-shaken, and the Nitro dev server exposes the workflow web UI at /_workflow for inspection, monitoring, and debugging of live runs.
The full integration details, including how dependency tracing interacts with workflow state and what the tree-shaking behavior means for complex step graphs, are in the getting-started guide at workflow-sdk.dev/v5/docs/getting-started/nitro. Read the original Vercel changelog for the release scope.
[READ ORIGINAL →]