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-stack/codegen-messaging

v0.1.1

Published

L2 messaging surface package for @pattern-stack/codegen — the canonical Channel/Message vocabulary, the MessagingPort composing contract, the bot-user write seam, and DI tokens. See ADR-036 + swe-brain ADR-0008.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

dugsnodesdugsnodes

Keywords

Readme

@pattern-stack/codegen-messaging

L2 messaging surface package for @pattern-stack/codegen (ADR-036). The type-shaped home for the messaging context: the canonical Channel / Message vocabulary, the MessagingPort composing contract, the bot-user write seam, the capability descriptor, and DI tokens.

Designed against swe-brain ADR-0008 (MessagingDomain, Slack first). Messaging is an interaction surface — incremental-read, no L2 sub-ports — so this package mirrors codegen-transcript rather than the CRM-shaped codegen-crm.

What's here (L2)

  • CanonicalChannel, CanonicalMessage (canonical.ts) — the vendor-agnostic Ts a provider adapter reads into (IChangeSource<Canonical…> → differ → sink). Vendor DTO → External(Zod) → canonical; vendor shapes never cross the boundary (hard rule #4).
  • MessagingPort (messaging.port.ts) — the single contract a messaging provider adapter implements: L1 auth + per-entity changeSources + the capabilities descriptor, plus an optional bot-user write seam. Entity-agnostic (named for the context, not an entity); reads go through the change-source registry.
  • MessagingCapabilities / NO_MESSAGING_CAPABILITIES (capabilities.ts) — runtime coverage (entities) + optional write availability (canWrite).
  • tokens (tokens.ts) — MESSAGING_PORT, MESSAGING_CAPABILITIES, MESSAGE_WRITE.
  • assertMessagingAdapter (@pattern-stack/codegen-messaging/testing) — the conformance / falsifier helper, kept out of the runtime barrel.

What's NOT here

  • Conversation — a derived grouping produced by the domain segmentation step (ADR-0008 §8), not vendor-sourced. No canonical read type, no change source; it lives only as a consumer entity + a domain-service output.
  • Composition — which providers/ports a given app wires is L3, in the consumer app, never in this package (ADR-036 §3).

Status

MessagingPort and the MessageWrite capability are provisional until a second vendor (Teams/Discord) passes assertMessagingAdapter — then they promote to stable (hard rule #8). The write path ships dark in v1 (ADR-0008 §9): the seam is built and wired, but chat:write is requested and no nudge fires only once the actuator activates.