npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@voyantjs/workflows

v0.107.10

Published

Authoring SDK for Voyant Workflows — durable, step-based orchestrations for Voyant Cloud.

Readme

@voyantjs/workflows

Authoring SDK for Voyant Workflows — durable, step-based orchestrations for Voyant Cloud.

import { workflow } from "@voyantjs/workflows";
import { z } from "zod";

export const sendBookingReminders = workflow({
  id: "send-booking-reminders",
  input: z.object({ bookingId: z.string() }),

  async run(input, ctx) {
    const booking = await ctx.step("fetch", () => db.bookings.findById(input.bookingId));

    await ctx.sleep("24h");

    await ctx.step("send-reminder", async () => {
      await email.send(booking.customerEmail, "Reminder...");
    });
  },
});

Subpaths

  • @voyantjs/workflows — authoring API (workflow, workflows, trigger, conditions, errors).
  • @voyantjs/workflows/client — app/server-safe managed Cloud client and Cloud-mode driver. Use this from app code that only needs workflows.trigger(...) or event forwarding; it does not import workflow definitions, runner code, or Node-only workflow dependencies.
  • @voyantjs/workflows/testing — in-process test harness (runWorkflowForTest, resumeWorkflowForTest).
  • @voyantjs/workflows/handler — tenant-side step handler for the v1 wire protocol. Mount at POST /__voyant/workflow-step in your Worker: export default { fetch: createStepHandler() }.
  • @voyantjs/workflows/auth — paired HMAC signer + verifier for the X-Voyant-Dispatch-Auth header. Wires into the orchestrator's sign hook and the handler's verifyRequest hook with a shared secret.
  • @voyantjs/workflows/bindings — runtime binding types and env shim for workflow code that reads platform bindings.
  • @voyantjs/workflows/configdefineConfig and voyant.config.ts types.
  • @voyantjs/workflows/errors — typed user/runtime errors (FatalError, RetryableError, TimeoutError, and related classes).
  • @voyantjs/workflows/protocol — wire-protocol types shared with the orchestrator.

Managed Cloud runtime split

Managed Voyant Cloud runs workflow bundles in the hosted Cloud runtime. App bundles should import only @voyantjs/workflows/client and call workflows.trigger(...); workflow definition files keep importing workflow(...), ctx.step(...), ctx.sleep(...), and trigger.on(...) from @voyantjs/workflows.

Cloud deployments inject:

VOYANT_CLOUD_WORKFLOWS_URL
VOYANT_CLOUD_WORKFLOW_TRIGGER_TOKEN
VOYANT_CLOUD_APP_SLUG
VOYANT_CLOUD_ENVIRONMENT

The client posts trigger calls to the app-scoped Cloud API. The Cloud-mode driver forwards event ingest to the same boundary, but workflow release registration is disabled by default: Cloud creates releases from deployments, artifacts, hashes, and environment snapshots. Existing self-host Node/Docker and Cloudflare runtimes continue to use the driver/orchestrator packages directly.

Full contract