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

@pattern-js/core

v0.2.2

Published

Pattern execution engine — runtime-neutral core (Web-standard APIs only).

Readme

@pattern-js/core

The runtime-neutral Pattern execution engine. Plain TypeScript over Web standards (Web Streams, AbortController, fetch, crypto.subtle). One dependency: Zod.

npm install @pattern-js/core
import { Engine, type Workflow } from "@pattern-js/core";

const engine = new Engine();              // base op catalog auto-registered
engine.registerWorkflow(wf);              // validates with human-readable errors
const result = await engine.run(wf, { input: { /* trigger ports */ } });

What's inside

  • Types & contractsPortSpec, OpDefinition, Workflow, Principal, hook/event/observability interfaces.
  • Validation — load-time checks (op/port existence, edge kind & schema compatibility, cycles, boundary pairing) with located, human-readable errors.
  • Scheduler — value barriers + control pulses + backpressured stream fan-out; skip propagation for branches; sub-workflow invocation.
  • Op catalog — constants, scalars, strings, objects, arrays (+ higher-order), control flow, data/encoding, time, crypto, http.fetch, the stream ops, WebSocket ops, hooks/events. Browse the generated reference at /docs/ops.
  • Boundaries — contracts + payload schemas (HTTP, WS, CLI, manual, schedule, hook, event).
  • Hooks & events, auth (Principal + provider chain), observability (OTLP-shaped spans), transport (in-process; pluggable).

Subpath exports: @pattern-js/core (everything), @pattern-js/core/ops, @pattern-js/core/boundaries.

Key APIs

| | | |---|---| | new Engine(opts?) | the façade: registries, services, transport, trace fan-out | | engine.registerWorkflow(wf) | validate + register (auto-wires boundary.hook / boundary.event) | | await engine.registerWorkflowAsync(wf) | same, but runs the resolve phase for boundary config ports | | engine.run(wf, { trigger?, input?, params?, principal? }) | run; returns RunResult | | engine.registerOp(op) / engine.use(mod) | extend with ops / a plugin mod | | engine.onTrace(sink) | subscribe to telemetry | | engine.invokeHook(name, payload) / engine.emit(event, payload) | extensibility | | validateWorkflow(doc, ops) / formatGraph(wf, ops) | validate / render |

See authoring ops, concepts, and architecture.