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

qqueue-sdk

v0.2.0

Published

TypeScript SDK for the self-hosted QQueue email API.

Readme

qqueue-sdk

TypeScript SDK for the self-hosted QQueue email API.

License

The QQueue SDK is licensed under the MIT License. See LICENSE.

Install

npm install qqueue-sdk

Usage

import { QQueueClient } from "qqueue-sdk";

const qqueue = new QQueueClient({
  apiKey: process.env.QQUEUE_API_KEY!,
  baseUrl: "https://mail.example.com/api/v1"
});

const email = await qqueue.sendEmail({
  to: "[email protected]",
  subject: "Welcome",
  html: "<p>Hello from QQueue.</p>",
  text: "Hello from QQueue."
});

console.log(email.id, email.status);

Templates

await qqueue.sendEmail({
  to: "[email protected]",
  templateId: "tpl_123",
  variables: {
    firstName: "Ada",
    resetUrl: "https://app.example.com/reset/token"
  }
});

The API key determines the QQueue organization, so SDK calls do not include an organizationId.

Choosing who it sends as

The From header comes from a sending account configured in QQueue, so you never set it on the request. Name the account by the address it sends as:

await qqueue.sendEmail({
  from: "[email protected]",
  to: "[email protected]",
  replyTo: "[email protected]",
  subject: "Welcome",
  text: "Hello."
});

Omit from and the organization's default sending account is used. Pass smtpConnectionId instead to name an account by id (it wins if you send both). An address no sending account uses is a 404, not a fall back to the default.

replyTo is optional twice over: leave it out and the send inherits whatever default Reply-To the sending account has, if any.

Errors

import { QQueueClient, QQueueError } from "qqueue-sdk";

try {
  await qqueue.sendEmail({
    to: "[email protected]",
    subject: "Welcome",
    text: "Hello"
  });
} catch (error) {
  if (error instanceof QQueueError) {
    console.error(error.status, error.code, error.message);
  }
}

Self-Hosting

Point baseUrl at your QQueue API URL. For example, if QQueue is hosted at https://mail.example.com, use:

const qqueue = new QQueueClient({
  apiKey: process.env.QQUEUE_API_KEY!,
  baseUrl: "https://mail.example.com/api/v1"
});

Releases

See CHANGELOG.md for version history and RELEASE.md for the publishing checklist, install smoke test, and version bump flow.