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

@structure-ai/cqrs

v0.0.9

Published

Schema-typed command/query buses with validation, authorization, idempotency and tracing middleware.

Readme

@structure-ai/cqrs

Logical CQRS: Schema-typed commands and queries, one handler per message, buses as Effect services. Every dispatch goes through the same pipeline: boundary validation (shape only — business rules stay in the domain) → authorization → idempotency (commands) → traced, measured handler execution.

Usage

import { Command, CommandBus, CommandHandler, HandlerRegistry, layer } from "@structure-ai/cqrs";
import { Effect, Schema } from "effect";

const ApproveInvoice = Command.define("ApproveInvoice", {
  payload: Schema.Struct({ invoiceId: Schema.String, approver: Schema.String }),
  success: Schema.Struct({ invoiceId: Schema.String, version: Schema.Number }),
});

const handlers = HandlerRegistry.layer(
  CommandHandler.make(ApproveInvoice, (payload, dispatch) =>
    Effect.succeed({ invoiceId: payload.invoiceId, version: 2 }),
  ),
);

const program = Effect.gen(function* () {
  const bus = yield* CommandBus;
  const ack = yield* bus.dispatch(ApproveInvoice, { invoiceId: "inv-1", approver: "ada" }, {
    idempotencyKey: "req-42",
  });
}).pipe(Effect.provide(layer.pipe(Layer.provide(handlers)))); // convenience layer: both buses, allow-all authorizer, in-memory idempotency

Exports

| Export | What it is | | --- | --- | | Command.define(tag, { payload, success, failure? }) / Query.define | Intent-named message definitions; failure types the handler's error channel (in-process only). | | CommandHandler.make / QueryHandler.make | Bind a definition to a handler (payload, dispatch) => Effect; dispatch carries messageId, correlationId, causationId, actor, idempotencyKey. | | HandlerRegistry.layer(...registrations) | Collects handlers (duplicate tag = defect at build time); captures handler service requirements from the context at build — satisfy them with Layer.provideMerge, not Layer.provide, or the services are spent building the registry and missing from the runtime context (missing-service defects at dispatch, invisible to the type checker). | | CommandBus / QueryBus (+ .layer, convenience layer) | dispatch(definition, input, { idempotencyKey?, actor?, timeout? }). | | Authorizer (+ allowAll) | Hook authorizing the requested action (tag/kind/actor/payload), not the endpoint. | | IdempotencyStore (+ inMemory) | Completed keys replay the cached success without re-running the handler. Durable exactly-once belongs to @structure-ai/eventsourcing's inbox. | | HandlerNotFound, Unauthorized, DispatchTimeout | Tagged errors with classification; validation failures reuse ValidationFailed from @structure-ai/domain. |

Each dispatch runs in a span (cqrs.command.<Tag>), a metrics boundary (calls/errors/latency), and Correlation.within with causationId = messageId.