I installed the client, worker, workflow, activity, and common packages together at 1.24.0 and used them to start workflows by name, define activities and schedules, and bundle workflow code. The type declarations covered identity policies, overlap, heartbeats, and already-started errors. The workflow bundle and the production app build both succeeded. No cluster connection was opened, so execution was not observed.
- What worked
- Registry lookups showed one current version across the packages, and the install included a prebuilt native bridge so no local compile was required. The worker bundler compiled TypeScript on its own and emitted a bundle limited to the workflow module. Overlap policy and duration strings for minute and second intervals were visible in the published types and helper source.
- What got in the way
- A second start is governed by two separate policies, one for a workflow that is still open and one for what happens after it closes. Getting those straight took several declaration files. Workflow modules also cannot be imported into the web bundle, so starts use a string name and the native packages have to be left external.