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

@mailqa/client

v0.1.0

Published

Official MailQA client — capture and assert on test email from automated suites.

Readme

@mailqa/client

Capture and assert on test email from automated suites — no sleep(), no mail-log scraping.

npm install --save-dev @mailqa/client

Quick start

import { MailQA } from '@mailqa/client';

const mailqa = new MailQA({ apiKey: process.env.MAILQA_API_KEY! });

// One throwaway inbox per test run keeps suites isolated.
const inbox = await mailqa.inboxes.create({ name: `ci-${process.env.GITHUB_RUN_ID}` });

await registerUser(inbox.address);           // your app under test

const message = await mailqa.waitForMessage({
  inbox: inbox.id,
  subjectContains: 'Verify your email',
  timeout: 30_000,
});

expect(message.html).toContain('Welcome');
await page.goto(message.links[0].url);

await mailqa.inboxes.delete(inbox.id);       // teardown

Getting mail in

Either point your app's SMTP config at the inbox's own credentials:

const inbox = await mailqa.inboxes.create({ name: 'ci' });
// inbox.smtp -> { host, ports: [587, 2525], username, password }

…or send to inbox.address ([email protected]) over the public internet. Both land in the same inbox and read identically through this client.

Waiting

waitForMessage polls until something matches or the timeout expires.

By default no time filter is applied — the email you are waiting for has usually already been sent by the time you call this, so filtering on "now" would race with it. Isolation comes from using a fresh inbox per test. When you deliberately reuse an inbox, pass after:

const t0 = new Date();
await triggerPasswordReset(inbox.address);
await mailqa.waitForMessage({ inbox: inbox.id, after: t0 });

Shortcuts for the two most common assertions:

const code = await mailqa.waitForCode({ inbox: inbox.id });          // "483920"
const link = await mailqa.waitForLink({
  inbox: inbox.id,
  matching: /\/verify\?/,
});

On timeout you get a MessageTimeoutError carrying the filter you used — which is what you need to debug "the email never arrived".

API

| Call | Purpose | |---|---| | inboxes.create({ name, address?, projectId? }) | New inbox, with SMTP credentials attached | | inboxes.list() / inboxes.delete(id) | Manage inboxes | | inboxes.empty(id) | Delete every message — test teardown | | messages.list(inboxId, filters) | Cursor-paginated search (to, from, subjectContains, q, tag, unread, since) | | messages.get(id) | Full message: text, sanitised html, rawHtml, links, codes, headers, attachments, SPF/DKIM/DMARC | | messages.raw(id) | The original .eml | | messages.attachment(id) | Attachment bytes | | messages.markRead(id) / messages.delete(id) | Housekeeping |

Errors are MailQAError with a stable code — branch on that, not the message.

Self-hosting

new MailQA({ apiKey, baseUrl: 'https://mailqa.internal' });

Full documentation