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

@hazeljs/flow

v1.0.3

Published

Durable execution graph engine - in-memory by default, optional Prisma persistence

Readme

@hazeljs/flow

npm version npm downloads License: Apache-2.0

Durable execution graph engine ("workflow OS kernel"). Fully independent of Hazel core.

Storage: By default the engine uses in-memory storage (no database). For durable persistence, install @prisma/client and use the Prisma storage adapter (see Persistence).

Features

  • Flow definitions (nodes + edges)
  • Flow runs with stateful execution
  • In-memory by default; optional Postgres persistence via Prisma
  • Audit event timeline
  • Retry/backoff, timeouts
  • Idempotency keys
  • WAIT state + resume
  • Optional Postgres advisory locks when using Prisma storage

Installation

pnpm add @hazeljs/flow

No database or env vars are required for the default in-memory mode.

Usage

Decorator-based (recommended)

import { FlowEngine, Flow, Entry, Node, Edge, buildFlowDefinition } from '@hazeljs/flow';
import type { FlowContext, NodeResult } from '@hazeljs/flow';

@Flow('my-flow', '1.0.0')
class MyFlow {
  @Entry()
  @Node('start')
  @Edge('end')
  async start(): Promise<NodeResult> {
    return { status: 'ok', output: 1 };
  }

  @Node('end')
  async end(ctx: FlowContext): Promise<NodeResult> {
    return { status: 'ok', output: ctx.outputs.start };
  }
}

const engine = new FlowEngine();
const def = buildFlowDefinition(MyFlow);
await engine.registerDefinition(def);

const { runId } = await engine.startRun({
  flowId: 'my-flow',
  version: '1.0.0',
  input: {},
});

let run = await engine.getRun(runId);
while (run?.status === 'RUNNING') {
  run = await engine.tick(runId);
}

Functional builder (alternative)

import { FlowEngine, flow } from '@hazeljs/flow';

const def = flow('my-flow', '1.0.0')
  .entry('start')
  .node('start', async (ctx) => ({ status: 'ok', output: 1 }))
  .node('end', async (ctx) => ({ status: 'ok', output: ctx.outputs.start }))
  .edge('start', 'end')
  .build();

Persistence

By default the engine uses in-memory storage. To persist runs and definitions to Postgres:

  1. Install Prisma client: pnpm add @prisma/client
  2. Set DATABASE_URL and run migrations (from this package’s prisma/ schema).
  3. Create the engine with Prisma storage:
import { FlowEngine, buildFlowDefinition } from '@hazeljs/flow';
import { createPrismaStorage, createFlowPrismaClient } from '@hazeljs/flow/prisma';

const prisma = createFlowPrismaClient();
const engine = new FlowEngine({ storage: createPrismaStorage(prisma) });
// ... register definitions, start runs, etc.

The migration SQL in prisma/migrations/ is only needed when you use this adapter.

Scripts

  • prisma:generate - Generate Prisma client
  • prisma:migrate - Run migrations (dev)
  • prisma:deploy - Deploy migrations (prod)
  • prisma:studio - Open Prisma Studio
  • test - Run Vitest tests

License

Apache 2.0 © HazelJS