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

@c11/notifications-nestjs

v1.0.5

Published

NestJS module for notifications: in-app and email channels, TypeORM-backed storage, and pluggable resolvers and content providers.

Downloads

348

Readme

@c11/notifications-nestjs

NestJS module for notifications: in-app and email channels, TypeORM-backed storage, and pluggable resolvers and content providers.

Installation

npm install @c11/notifications-nestjs

Peer dependencies: @nestjs/common, @nestjs/core, @nestjs/schedule, @nestjs/typeorm, typeorm, reflect-metadata. Ensure your app has them installed.

Usage

Register the module with forRoot() and optional overrides:

import { NotificationsModule } from "@c11/notifications-nestjs";

@Module({
  imports: [
    NotificationsModule.forRoot({
      imports: [YourConfigModule], // modules that export your custom providers
      providers: [
        { provide: NotificationEmailResolver, useClass: YourEmailResolver },
        { provide: NotificationEmailContentProvider, useClass: YourEmailContentProvider },
        // optional: NotificationMailSender, NotificationInAppContentProvider
      ],
    }),
  ],
})
export class AppModule {}
  • NotificationEmailResolver: resolve email for a receiver (user id).
  • NotificationEmailContentProvider: build subject/body for email deliveries.
  • NotificationMailSender: send emails (default: console logger).
  • NotificationInAppContentProvider: build in-app content (default: minimal).

Exported services: NotificationsService, NotificationRepository, NotificationDeliveryRepository, and channel handlers as needed.

Database (TypeORM)

The module uses two entities:

  • NotificationEntity → table notifications
  • NotificationDeliveryEntity → table notification_deliveries and join table notification_delivery_notifications

Include the provided entities in your TypeORM setup so the schema is known to TypeORM. When you import NotificationsModule, it registers these entities via TypeOrmModule.forFeature(). If your app uses TypeOrmModule.forRoot({ autoLoadEntities: true }), they are picked up automatically. Otherwise, add NotificationEntity and NotificationDeliveryEntity (imported from @c11/notifications-nestjs) to your TypeORM root config or feature modules so they are part of your DataSource.

Generate a migration for your database from these entities using TypeORM’s migration generator (e.g. npm run typeorm migration:generate -- -n AddNotifications or your app’s equivalent). Then run the migration. This package does not ship migration files; the consuming app is responsible for generating and running migrations.

License

PRIVATE