better-notify
Better Notify
End-to-end typed notification infrastructure for Node.js (ESM-only, Node >= 22). A single catalog type drives the typed sender and webhook router — analogous to tRPC, but for notifications.
When to use
When setting up typed notifications, adding email/SMS/push transports, defining notification catalogs, or answering questions about @betternotify/* packages.
Skills
- setup — Interactive setup wizard. Scans your project, asks what channels/transports you need, and scaffolds the catalog + client.
- best-practices — Quick reference for configuration, channel slots, subpath imports, middleware, hooks, and common gotchas.
Core Concepts
Catalog — Typed contract defining notification routes. Built with createNotify(), composed via .catalog(). Sub-catalogs flatten into dot-path IDs (transactional.welcome).
Client — Type-safe sender derived from a catalog. createClient() returns mail.<route>.send(input) and .render().
More from ali-master/skills
orpc ecosystem
Community resources, starter kits, tools, and libraries for oRPC.
2orpc event iterator (sse)
Streaming responses, real-time updates, and server-sent events using oRPC.
2orpc comparison
How oRPC differs from tRPC, ts-rest, and Hono.
2orpc openapilink
Use OpenAPILink in oRPC clients to communicate with OpenAPI-compliant APIs.
2orpc middleware
Middleware enables reusable and extensible procedures in oRPC.
2orpc metadata
Enhance your procedures with metadata.
2