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

@021.is/spine-email

v0.4.3

Published

Resend wrapper with structured logging, retries, and a uniform send API. Templates live in the consuming app.

Readme

@021.is/spine-email

Resend wrapper. Bearer auth, retry on 5xx, terminal on 4xx (no infinite-loop on permanent client errors), idempotency-key passthrough, structured logging hook.

Use

import { makeEmailClient } from "@021.is/spine-email";

const email = makeEmailClient({
  apiKey: env.RESEND_API_KEY,
  defaultFrom: "My App <[email protected]>",
  retries: 2,
  logger: console, // optional pino-compatible logger
});

await email.send({
  to: "[email protected]",
  subject: "Welcome to My App",
  html: renderToString(<WelcomeEmail name="Sam" />),
  tags: { app: "my-app", flow: "signup" },
  idempotencyKey: `signup-${userId}`,
});

Behavior

  • 5xx → up to retries more attempts (default 2)
  • 4xx → throws SomethingWentWrongException immediately, no retries (4xx is permanent — looping wastes time + money)
  • Missing both html and text → throws
  • Sets idempotency-key header when provided (Resend dedupes server-side)

React Email templates

Templates live in the consuming app (React Email, MJML, plain HTML — your call). spine-email is just the transport.

Why not just fetch

Default fetch has no retry, no logging, no terminal-on-4xx logic, no idempotency. After the third app reimplemented it, it became a package.