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

@adatechnology/notification-contracts

v0.1.0-rc.6

Published

Shared types, zod schemas, and port interfaces for the notification trio (contracts only — no runtime behavior)

Readme

@adatechnology/notification-contracts

Tipos, schemas zod e portas do trio de notificações. Sem comportamento de runtime — o módulo valida com ele, os drivers implementam as portas dele, o frontend tipa as chamadas com ele, e mudança de contrato quebra todos em compile-time em vez de em produção.

Única dependência: zod.

Instalação

bun add @adatechnology/notification-contracts

O que traz

| Área | Conteúdo | |---|---| | Entidades | Notification, Delivery, Device, Preference, Template, Suppression | | Canais | NOTIFICATION_CHANNELinbox, push, email, whatsapp | | Portas de driver | PushDriverPort, EmailDriverPort, WhatsAppDriverPort, InboxDriverPort | | Portas do host | RecipientResolverPort, QueuePort, RealtimeNotifierPort, LoggerPort | | Entrada | sendNotificationSchema, registerDeviceSchema, updatePreferencesSchema, … | | Eventos | hooks de ciclo de vida da entrega | | Erros | NotificationError e subclasses, com statusCode e code estáveis |

DeliveryAttemptResult é união discriminada

type DeliveryAttemptResult =
  | { outcome: 'sent'; providerMessageId?: string }
  | { outcome: 'retriable'; errorCode: string; message: string }
  | { outcome: 'permanent'; errorCode: string; message: string }
  | { outcome: 'invalid-target'; errorCode: string; message: string }

Quem classifica é o driver, nunca o módulo: só ele conhece o vocabulário de erro do provedor. invalid-target é separado de permanent porque tem consequência própria — o device é desativado ou o e-mail entra na lista de supressão, em vez de a fila insistir para sempre num token morto.

Invariantes

  • companyId nunca entra em schema de corpo. Vem do contexto autenticado do host.
  • Nenhum tipo de HTTP aqui. Rota é assunto do @adatechnology/module-http; este pacote é domínio. Um contracts que conhece a palavra "rota" acaba amarrado ao transporte.
  • Nenhuma porta valida token. O host resolve identidade e entrega pronta (security.md §2).
  • Alvo de entrega (telefone, e-mail) nunca aparece cru em log — ver maskTarget/hashTarget no módulo.

Licença

MIT © Ada Technology