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

@xeplr/email

v1.0.0

Published

Internal email HTTP API — lightweight server wrapping xeplr-utils email providers

Downloads

136

Readme

xeplr-email

Email service with multi-provider support, optional queue, CC, and file attachments.

Setup

var email = require('xeplr-email');

email.init({
  provider: 'smtp',          // 'smtp', 'aws', 'azure', or 'brevo'
  testTo: '[email protected]', // send test email on startup to verify health
  useQueue: true,             // optional: queue emails instead of sending immediately
  flushIntervalInSeconds: 5,  // queue flush interval (default: 5)
  maxEmptyTicks: 3,           // auto-pause after N empty ticks (default: 3)
  smtp: {
    host: 'smtp.example.com',
    port: 587,
    user: 'user',
    pass: 'pass',
    from: '[email protected]'
  }
});

Usage

send(to, subject, html, cc, attachments)

| Parameter | Type | Required | Description | |-------------|------------|----------|-------------| | to | string[] | yes | Recipient emails | | subject | string | yes | Email subject | | html | string | yes | HTML body | | cc | string[] | no | CC recipients | | attachments | string[] | no | File paths to attach |

Send a simple email

var email = require('xeplr-email');

email.send(['[email protected]'], 'Hello', '<p>Hi there</p>');

Multiple recipients

email.send(
  ['[email protected]', '[email protected]'],
  'Hello',
  '<p>Hi there</p>'
);

With CC

email.send(
  ['[email protected]'],
  'Hello',
  '<p>Hi there</p>',
  ['[email protected]', '[email protected]']
);

With attachments

Attachments are file paths — they get picked up and attached automatically.

email.send(
  ['[email protected]'],
  'Report',
  '<p>See attached report.</p>',
  [],                                       // cc (empty)
  ['/tmp/report.pdf', '/tmp/data.csv']      // attachments
);

With CC and attachments

email.send(
  ['[email protected]'],
  'Report',
  '<p>See attached.</p>',
  ['[email protected]'],
  ['/tmp/report.pdf']
);

Via HTTP API

Start as standalone server:

var email = require('xeplr-email');
email.start({ provider: 'smtp', useQueue: true, smtp: { ... } });

Then send via HTTP:

POST /internal/send
Content-Type: application/json

{
  "to": ["[email protected]"],
  "subject": "Hello",
  "html": "<p>Hi</p>",
  "cc": ["[email protected]"],
  "attachments": ["/tmp/report.pdf"]
}

Providers

| Provider | Config key | Required fields | |----------|-----------|----------------| | SMTP | smtp | host, port, user, pass, from | | AWS SES | aws | region, accessKeyId, secretAccessKey, from | | Azure | azure | connectionString, from | | Brevo | brevo | apiKey, fromEmail, fromName |

Queue behavior

When useQueue: true:

  • Emails are queued in memory, not sent immediately
  • Queue flushes every flushIntervalInSeconds (default: 5s)
  • Emails are sent one at a time, in order
  • Queue auto-pauses after maxEmptyTicks consecutive empty flushes
  • Queue auto-resumes when a new email is added

When useQueue: false (default):

  • Emails are sent immediately and send() returns a promise

Health check

When testTo is configured (or EMAIL_TEST_TO env var), a test email is sent on startup. Check health with:

email.isHealthy(); // true if test email was sent successfully