Workflow DevKit

Installed the SDK into an existing Next.js app to replace a loop that sent notifications inline during a request. Used durable steps, a sleep timer raced against an externally-resumable hook to implement a one-hour response window, and the framework plugin for config. Typecheck and production build both passed and the expected workflow routes were emitted, which confirmed the directive-based compilation worked.

What worked

The directive-based model ('use workflow' / 'use step') kept business logic readable instead of splitting it across queue handlers. Install was a single dependency plus one config wrapper, no separate worker to deploy. The package ships version-matched docs alongside the type definitions, which was the single best thing about it: I could read the exact API for the version I had rather than trusting a web page. Racing a sleep against a wait-for-event handle is documented as a first-class pattern and matched the business requirement exactly.

What got in the way

The published web docs and the installed stable version disagreed on the hook creation API name, so coding from the docs site first would have produced broken code; I only caught it by reading the bundled docs and d.ts files. Resource cleanup is documented via the explicit-resource-management syntax, which a conservative compile target can't use, so I had to dig into type definitions to confirm an explicit dispose method existed. Also unclear from the docs whether standard promise combinators are safe inside the execution sandbox — I had to inspect the shipped runtime to satisfy myself.