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

@xlambda-tech/email

v0.2.0

Published

xlambda managed email SDK: Resend-compatible sending, domain/DKIM setup, and a ready-made inbound-mail webhook handler.

Readme

@xlambda-tech/email

Send email from your own domain, and — the reason this package exists — turn on receiving with almost no glue code.

Receiving inbound mail

import { createInboundHandler } from '@xlambda-tech/email';

export const { POST } = createInboundHandler({
  secret: process.env.XLAMBDA_WEBHOOK_SECRET!,
  onReceived: async (msg) => {
    // msg is fully typed: domain, from, to, subject, textBody, htmlBody, headers, sizeBytes, truncated
    await db.inboundEmails.create({ data: msg });
  },
}).toNextRouteHandler();

That's the whole integration for a Next.js App Router route handler. Point your project's webhookUrl (dashboard → Settings → Webhooks) at this endpoint and inbound mail on your managed domain starts landing in your own database.

This is the only place a message's body ever exists. The platform stores no message content server-side by design — only metadata (from, to, subject, size) shows up in client.domains.messages(). If your handler doesn't persist what it needs on receipt, it's gone (deliveries do retry 3× with exponential backoff if your endpoint errors, so a transient failure isn't fatal — a onReceived that never runs at all is).

Other frameworks:

import { toExpressHandler } from '@xlambda-tech/core/webhooks/adapters/express';
import { toFastifyPlugin } from '@xlambda-tech/core/webhooks/adapters/fastify';

// Express - MUST be mounted behind express.raw(), not express.json()
app.post('/webhooks/email', express.raw({ type: 'application/json' }), toExpressHandler(handler));

// Fastify - registers its own route + raw-body content-type parser, scoped to this plugin only
fastify.register(toFastifyPlugin(handler), { prefix: '/webhooks/email' });

// Raw Node http
const server = http.createServer(handler.toNodeHandler());

onSent/onDelivered/onBounced are also available on createInboundHandler for the outbound-side events, if you want one endpoint handling everything.

Sending

import { EmailClient } from '@xlambda-tech/email';

const client = new EmailClient({ apiKey: process.env.XLAMBDA_API_KEY! });

await client.emails.send({
  from: '[email protected]',
  to: '[email protected]',
  subject: 'Hello',
  html: '<p>Hi there</p>',
});

Resend-compatible shape (from/to/cc/bcc/replyTo/subject/text/html). from's domain must belong to a domain your project owns and has verified.

Setting up a domain

const domain = await client.domains.create({ projectId, domain: 'yourdomain.com' });
// domain.dkimRecords -> publish these at your DNS registrar
await client.domains.verify(domain.id); // re-checks MX/SPF/DKIM/DMARC once published

Checking message history

const { messages } = await client.domains.messages(domain.id, { direction: 'received', limit: 50 });

Metadata only (from/to/subject/status/size) — for the full body of a received message, you must have captured it via createInboundHandler at receipt time (see above).