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

@mailsurge/node

v1.0.0

Published

Official Mailsurge SDK for Node.js

Downloads

21

Readme

Mailsurge Node.js SDK

GitHub Tests Action Status

Official Node.js client for the Mailsurge transactional email API.

Requirements

  • Node.js 18+ (native fetch)

Installation

npm install @mailsurge/node

Usage

Set your API key in the environment:

MAILSURGE_API_KEY=sk_yourkey

Send a message:

import Mailsurge from '@mailsurge/node';

const mailsurge = new Mailsurge();

await mailsurge.messages.send({
  from: 'Acme <[email protected]>',
  to: ['[email protected]'],
  subject: 'Welcome to Acme',
  html: '<p>Your account is ready.</p>',
  text: 'Your account is ready.',
});

Pass the key explicitly when you prefer not to use environment variables:

const mailsurge = new Mailsurge({ apiKey: process.env.MAILSURGE_API_KEY });

Attachments and headers

await mailsurge.messages.send({
  from: 'Sender <[email protected]>',
  to: '[email protected]',
  subject: 'Hello',
  html: '<p>See attached.</p>',
  headers: {
    'X-Campaign': 'welcome',
  },
  attachments: [
    {
      filename: 'hello.txt',
      content: Buffer.from('Hello world!').toString('base64'),
      content_type: 'text/plain',
      disposition: 'attachment',
    },
  ],
});

Error handling

Non-2xx responses raise typed errors:

import {
  MailsurgeAuthenticationError,
  MailsurgeRateLimitError,
  MailsurgeValidationError,
} from '@mailsurge/node';

try {
  await mailsurge.messages.send({ /* ... */ });
} catch (error) {
  if (error instanceof MailsurgeRateLimitError) {
    console.error('Limit:', error.body.limit);
  }
}

Configuration

| Variable | Description | | --- | --- | | MAILSURGE_API_KEY | API key from the Mailsurge dashboard | | MAILSURGE_API_URL | Optional API base URL (defaults to https://mailsurge.dev) |

Testing

npm test

License

MIT. See LICENSE.