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

@c9up/rover

v0.1.8

Published

Mail transport for Ream — SMTP, log, and pluggable transports

Readme

@c9up/rover

Mail transport for Ream — SMTP, log, and pluggable transports (Mailgun, SendGrid, SES, Resend), plus class-based mailers (BaseMail), async templating (htmlView), in-process retry with exponential backoff, and an optional queue path via @c9up/bay.

Quick start

import { Mail } from '@c9up/rover'
import '@c9up/rover/transports/mailgun' // opt-in side-effect registration

const mail = new Mail({
  default: 'mailgun',
  from: '[email protected]',
  transports: {
    mailgun: { transport: 'mailgun', apiKey: process.env.MAILGUN_KEY!, domain: 'mg.acme.com' },
  },
})

await mail.send((m) => m.to('[email protected]').subject('Welcome').html('<p>Hi</p>'))

Webhooks

Providers push delivery events (delivered, bounced, failed) to a URL you configure. Rover ships signature-verifying middleware for Mailgun, SendGrid, and Resend that emit canonical mail.* events into your event bus.

import { createMailgunWebhookHandler } from '@c9up/rover/webhooks/mailgun'
import { Emitter } from '@c9up/ream/events'

const emitter = app.container.resolve(Emitter)

router.post(
  '/webhooks/mailgun',
  createMailgunWebhookHandler({
    signingKey: process.env.MAILGUN_SIGNING_KEY!,
    emitter,
    // maxAgeSeconds: 300 (default) — rejects replayed-old signatures
  }),
)

The handler verifies the HMAC over timestamp + token, enforces a ±5 minute replay window, and emits mail.delivered / mail.bounced / mail.failed on the bus. Invalid / stale / missing signatures return 401 without leaking internals.

SendGrid (Ed25519 via x-twilio-email-event-webhook-signature) and Resend (Svix HMAC via svix-signature) use the same API shape:

import { createSendGridWebhookHandler } from '@c9up/rover/webhooks/sendgrid'
import { createResendWebhookHandler } from '@c9up/rover/webhooks/resend'

router.post('/webhooks/sendgrid', createSendGridWebhookHandler({
  publicKey: process.env.SENDGRID_WEBHOOK_PUBLIC_KEY!,
  emitter,
}))

router.post('/webhooks/resend', createResendWebhookHandler({
  secret: process.env.RESEND_WEBHOOK_SECRET!, // accepts both `whsec_...` and raw base64
  emitter,
}))

rawBody() contract

All three handlers rely on ctx.request.rawBody() returning the exact bytes the provider signed. If your framework re-parses the body into JSON before the handler sees it and your rawBody() returns a re-serialised copy, bytes differ and every signature fails. Mount these handlers on a route where the raw body is preserved (e.g. skip the JSON body parser on /webhooks/**).

Queue / sendLater

Register @c9up/bay's QueueManager in your container and Rover will pick it up automatically:

import '@c9up/rover/transports/mailgun'
import { QueueManager, MemoryDriver } from '@c9up/bay'

app.container.singleton('QueueManager', () => new QueueManager(new MemoryDriver()))

// Then in a request handler:
await mail.sendLater((m) => m.to('[email protected]').subject('Welcome').html('<p>Hi</p>'))
// returns a job id string; the actual send runs on the Bay worker.

Without a QueueManager wired, sendLater falls back to an in-memory messenger (immediate microtask dispatch) — matching @adonisjs/mail's MemoryQueueMessenger. It never throws for a missing queue.

Testing

import '@c9up/rover/transports/mailgun' // register whatever transports your app uses

const fake = mail.fake()
await userRegistration({ email: '[email protected]' })
fake.assertSent({ to: '[email protected]', subject: 'Welcome' })
mail.restore()