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

@damatjs/provider

v1.0.6

Published

ModuleService-based provider authoring and role binding contracts for Damat

Readme

@damatjs/provider

The provider authoring layer for Damat. A provider is an ordinary module whose service follows an additional, repeatable contract. It uses the same models, credentials, migrations, generated accessors, transactions, initialization, and routes as every other module.

ProviderService extends ModuleService and adds a stable role marker:

import { ProviderService } from "@damatjs/provider";
import { models } from "./models";

abstract class EmailProviderService extends ProviderService({
  role: "email",
  models,
}) {
  abstract send(input: SendEmailInput): Promise<SendEmailResult>;
}

Provider-standard packages use that pattern to declare abstract operations. Concrete modules implement the operations and fail TypeScript compilation when a required method is missing. A plain ModuleService with the same structural methods can also fill a provider role.

The backend initializes the module once and binds its existing service:

modules: {
  mail: { resolve: "./src/modules/mail" },
},
providers: {
  email: { module: "mail" },
}

The provider layer owns no factory context, database pool, routes, middleware, health lifecycle, or shutdown lifecycle. Those remain normal module/framework concerns.

License

MIT