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

@dheeai/runner-sdk

v0.5.0

Published

Authoring SDK for Dhee runners & bundles — the firewall a runner depends on.

Readme

@dheeai/runner-sdk

The public authoring SDK for Dhee runners and bundles.

dhee-core is a content-agnostic DAG engine that walks a bundle (a pipeline graph) and executes each node with a runner (a node executor). Runners ship as standalone npm packages the engine discovers at runtime — and they depend on this package only, never on dhee-core internals. That firewall lets the engine evolve without breaking the ecosystem, and lets you build, test, and publish a runner in isolation.

Install

npm install @dheeai/runner-sdk

What it gives you

  • defineRunner(impl) — wrap your { describe, run } into a Runner.
  • resolveEndpointUrl(name) — resolve a named endpoint (self.local, self.cloud, …) to its URL from the user's env (ENDPOINT_<name> / COMFYUI_BASE_URL). Keeps endpoint URLs out of bundles.
  • retryTransient(fn, opts) / isTransientError(e) — retry network/Comfy calls with backoff + abort support.
  • computeInputsHash(key) — content-addressed cache key for a node's inputs.
  • ffmpegBin() / ffprobeBin() — resolve the ffmpeg / ffprobe executable to spawn. See below.
  • ComfyClient — queue a workflow, poll for completion, download outputs. Handles local ComfyUI and Comfy Cloud (auth scheme, /api path prefix, history_v2, and the lagging-history + execution_error cases that otherwise look like a silent timeout).
  • pruneAndRedirect() / injectParameter() — pure Comfy workflow-graph edits: drop optional nodes and transitively repoint their consumers; set a value at a node/field with an actionable error when the node is gone.
  • resolveWorkflowPath() / isCloudEndpoint() — pick a _cloud.json workflow variant when the endpoint is Comfy Cloud, so a runner doesn't ship local model filenames to cloud.
  • buildComfyAuthHeaders() and friends — Bearer for the dhee proxy, X-API-Key for cloud.comfy.org, nothing locally.
  • The canonical types: Runner, RunnerContext, RunnerDescription, RunnerManifest, RunnerResult, RunnerArtifact, DagBundle, NodeDef, and the bundle/LLM-access types.

Driving a Comfy workflow

import {
  ComfyClient, resolveEndpointUrl, resolveWorkflowPath, pruneAndRedirect, injectParameter,
} from '@dheeai/runner-sdk';

const endpointUrl = resolveEndpointUrl(cfg.endpoint ?? 'self.local');
if (!endpointUrl) return { ok: false, error: 'no Comfy endpoint configured' };

// Cloud-aware: prefers foo_cloud.json when endpointUrl is Comfy Cloud.
const wfPath = resolveWorkflowPath({ workflowPath: cfg.workflowPath, bundleDir: ctx.bundleDir, endpointUrl });
const workflow = JSON.parse(await readFile(wfPath, 'utf-8'));

const client = new ComfyClient(endpointUrl);
const { name } = await client.uploadFile(inputImagePath);
injectParameter(workflow, { nodeId: '1', field: 'image' }, name);

// Optional inputs absent? Drop their nodes; consumers fall back transitively.
pruneAndRedirect(workflow, { deleteNodes: ['3', '13'], redirects: [{ from: '13', to: '12' }] });

const outs = await client.run(workflow, { signal: ctx.signal });
await client.download(outs[0], outputAbsPath);

Don't hand-write a Comfy client per runner — that is how the plumbing drifted across packages in the first place.

Spawning ffmpeg

Never spawn a bare 'ffmpeg'. It assumes a system ffmpeg on PATH, which does not exist on a clean Windows box, in CI without ffmpeg installed, or inside a macOS GUI app that never inherited the shell PATH. The failure is spawn ffmpeg ENOENT at render time — on someone else's machine.

Use the resolver instead:

import { ffmpegBin, ffprobeBin } from '@dheeai/runner-sdk';

spawn(ffmpegBin(), ['-i', input, ...args]);

Resolution order:

  1. dhee_FFMPEG_PATH / dhee_FFPROBE_PATH env override — lets a host (the desktop) or a power user pin a specific binary.
  2. The bundled installer binary, chmod +x'd if the package manager stripped execute bits, and rewritten from app.asar to app.asar.unpacked when running inside a packaged Electron app.
  3. Bare ffmpeg / ffprobe on PATH.

If your runner spawns ffmpeg, add the binaries to your own dependencies so step 2 can fire:

npm install @ffmpeg-installer/ffmpeg @ffprobe-installer/ffprobe

They are declared here as optional peer dependencies: the SDK provides the resolver, your runner provides the binaries. That way a runner that never touches ffmpeg doesn't pay for ~80 MB of platform binaries, and one that does gets a real executable on every platform.

Minimal runner

import { defineRunner, resolveEndpointUrl, retryTransient } from '@dheeai/runner-sdk';
import type { RunnerContext, RunnerDescription, RunnerManifest } from '@dheeai/runner-sdk';

export const manifest = {
  tool: 'my.thing',
  version: '0.1.0',
  engineCompat: '>=0.1.0',
  credentials: [],
  displayName: 'My Thing',
  description: 'Does a thing.',
  entry: 'dist/index.js',
  permissions: { network: ['<host>'], filesystem: 'project', subprocess: false, env: [] },
} satisfies RunnerManifest;

const describe = (): RunnerDescription => ({
  id: manifest.tool,
  displayName: 'My Thing',
  description: 'Does a thing.',
  capabilities: ['example'],
  modalities: { input: ['text'], output: ['image'] },
  configSchema: { type: 'object', required: ['outputPath'], properties: { outputPath: { type: 'string' } } },
});

async function run(ctx: RunnerContext) {
  // ... do work, write ctx.node.runner.config.outputPath under ctx.projectDir ...
  return { ok: true, outputPath: 'out.png' };
}

export const runner = defineRunner({ describe, run });

// Discovery entry — package.json "dhee.runners" points here.
export const runners = [{ manifest, runner }];

Discovery (how dhee-core finds your runner)

Your package opts in via name + keyword + entry point:

{
  "name": "dhee-runner-my-thing",
  "keywords": ["dhee-runner"],
  "dhee": { "runners": "./dist/index.js" },
  "dependencies": { "@dheeai/runner-sdk": "^0.1.0" }
}

npm create dhee-runner scaffolds all of this for you.

License

Apache-2.0