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/event

v0.2.0

Published

Versioned domain event contracts and identifiers for the event-driven platform.

Readme

@event-driven-platform/event

Defines domain event contracts and the event envelope used to carry execution metadata with emitted events.

Installation

pnpm add @event-driven-platform/event zod

zod is a peer dependency because EventContract accepts and exposes Zod schemas at its public TypeScript boundary. Applications should provide one compatible Zod installation for both their own schemas and this package.

Runtime Event contracts

Use one Zod-backed contract as the runtime and TypeScript source of truth for an Event's name, business schema version, and payload:

import { z } from 'zod';
import {
    defineEventContract,
    type EventEnvelopeOf,
    type EventOf,
    type EventPayloadOf,
} from '@event-driven-platform/event';

const DocumentRegistered = defineEventContract({
    name: 'documents.registered',
    schemaVersion: 1,
    payload: z.object({
        documentId: z.string(),
        storageReference: z.string(),
    }),
});

type Payload = EventPayloadOf<typeof DocumentRegistered>;
type DomainEvent = EventOf<typeof DocumentRegistered>;
type Envelope = EventEnvelopeOf<typeof DocumentRegistered>;

const event = DocumentRegistered.create({
    documentId: 'document-1',
    storageReference: 'storage-1',
});

const parsed = DocumentRegistered.parse(unknownEvent);

create() validates the payload and supplies the contract name/version. parse() validates an unknown Event against the exact contract identity and payload schema. The Zod output type is the payload type carried by the resulting Event.

schemaVersion is the business event-contract version. It is not a Schema Registry subject version or schema ID.

The runtime contract is additive: existing TypeScript-only Event<name, schemaVersion, payload> users remain supported, and contract-derived Events are structurally compatible with that boundary.

API

  • Event, AnyEvent — domain event contracts.
  • EventContract and defineEventContract — Zod-backed runtime Event contract definition, validation, and construction.
  • EventPayloadOf, EventOf, EventEnvelopeOf — types inferred from an Event contract.
  • EventId and DefaultEventIdFactory — deterministic event identity contracts and default factory.
  • EventEnvelope, AnyEventEnvelope — event plus metadata envelope.
  • EventActor and EventSubject — envelope metadata contracts.

Role

Operations may produce events as part of their result. Operations do not publish them. Runner persists event envelopes to the Outbox through the execution pipeline.

Runtime Event contracts remain transport-neutral. External payload schemas can be rendered independently as JSON Schema, Avro, or Protocol Buffers without adding renderer dependencies to this package.

Related documentation