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

@event-driven-platform/runner

v0.0.5

Published

Centralized execution engine for Commands, idempotency, policies, transactions, and Outbox persistence.

Downloads

541

Readme

@event-driven-platform/runner

The centralized execution engine for the platform's write pipeline.

Installation

pnpm add @event-driven-platform/runner

Runner is normally composed together with the persistence and handler-resolution contracts it depends on. Install the packages your application imports directly.

Role

Operation -> Command -> Runner

Runner executes Commands and owns infrastructure-centric execution behavior: idempotency, execution-log transitions, transaction coordination, handler resolution, guard evaluation, rate limiting, timeout, retry, result persistence, and Outbox persistence.

Operations and handlers must not reproduce or bypass these responsibilities.

Primary API

  • Runner / RunnerExecution — execution contract and typed execution result.
  • createRunner() / CreateRunnerOptions — supported Runner construction entry point.
  • RunnerDependencies — required and optional integration ports.
  • RunnerRuntime, RunnerOptions, RunnerResultSource — runtime/options/result metadata contracts.

Consumer-provided runtime ports

Runner exposes orchestration-specific ports for GuardEvaluator, RateLimiter, ExecutionTimeout, and RetryDelay. DefaultExecutionTimeout and DefaultRetryDelay are provided when the defaults are suitable.

The exported typed errors allow callers to distinguish execution conflicts, policy rejection, timeout, unavailable policy infrastructure, and rejected state transitions without parsing error messages.

Composition

A consuming application supplies adapters for execution-log persistence, execution transactions, Operation handler resolution, and Outbox persistence, then constructs Runner with createRunner(). Optional guard/rate-limit/runtime implementations are supplied only when those policies are used or overridden.

Execute Commands through Runner.execute(); do not call Operation handlers directly as an alternative execution path.

Related documentation