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

@dankolar06/notifications

v0.0.1

Published

Framework-agnostic contract layer for the Telemed notification system — types, payload Zod schemas, channel/event constants, and localized copy. Server-engine-free, safe to bundle into React Native.

Readme

@dankolar06/notifications

The consumer / contract layer of the Telemed backend notification system, extracted into a standalone, framework-agnostic npm package. It is meant to be imported by the React Native (Expo) patient/clinician app and by backend code that needs the shared notification contract.

Its only runtime dependency is zod. It contains zero server-only dependencies — no NestJS, no BullMQ, no Drizzle, no Medplum, no Node-only APIs — so it is safe to bundle into a mobile app.

What's inside

  • Types (src/types/) — pure record shapes and enums: event/delivery/group-bucket records, severity/status const arrays, inbox list result, preference shapes.
  • Constants (src/constants/) — TELEMED_NOTIFICATION_CHANNEL_KEYS (+ default list) and TELEMED_NOTIFICATION_EVENT_TYPES / TelemedNotificationEventType.
  • Payload schemas (src/payloads/) — the Zod payload schemas (and inferred types) for each notification domain: request-task, alarm, appointment, request/encounter chat, screening.
  • Localized copy (src/copy/) — cs/en tables for event titles, descriptions, severity labels, and appointment-type / status / priority maps, plus pure helpers: getEventTitle, getEventDescription, getSeverityLabel.
  • Utils (src/utils/) — pure helpers such as buildNotificationMessagePreview.

What's intentionally NOT here

The server engine stays in the backend and is deliberately excluded: the NestJS modules, BullMQ queues/processors, Drizzle channels, the delivery port/adapter interfaces, the recipient resolver, the publisher/orchestration types, and the server-side email/SMS/digest body builders (which depend on server record types and rendering). This package is the contract, not the runtime.

Usage (React Native / Expo)

import {
	requestTaskPayloadSchema,
	getEventTitle,
	getSeverityLabel,
	TELEMED_NOTIFICATION_CHANNEL_KEYS,
	type RequestTaskNotificationPayload,
	type NotificationListResult,
} from '@dankolar06/notifications'

const payload: RequestTaskNotificationPayload = requestTaskPayloadSchema.parse(rawPayload)

const title = getEventTitle('cs', 'request_task_created')
const severity = getSeverityLabel('cs', 'warning')

Build

npm install
npm run build   # emits dist/ with .js and .d.ts (+ declaration maps)