Email SDK

A lightweight TypeScript SDK for transactional email. Use one client in your app, pick the adapters you actually send through, and keep provider-specific field support visible in the docs.

Packages

• packages/email-sdk - core SDK, adapters, CLI, tests
• apps/fumadocs - documentation site
• skills/email-sdk - repo-local agent skill for Email SDK integrations

Quickstart

bun add @opencoredev/email-sdk

import { createEmailClient } from "@opencoredev/email-sdk";
import { resend } from "@opencoredev/email-sdk/resend";

const email = createEmailClient({
  adapters: [resend({ apiKey: process.env.RESEND_API_KEY! })],
});

await email.send({
  from: "Acme <hello@acme.com>",
  to: "user@example.com",
  subject: "Welcome",
  html: "<p>It works.</p>",
});

SMTP is built in and does not require Nodemailer.

Adapters are stable by contract: they map supported EmailMessage fields and reject unsupported fields instead of silently dropping them.

Agent Skill

Install the Email SDK agent skill from skills.sh when you want an AI agent to add, review, or document an integration:

npx skills add opencoredev/email-sdk --skill email-sdk

The skill is stored in skills/email-sdk/SKILL.md. It tells agents to refresh the current README, Fumadocs pages, package exports, and TypeScript declarations before implementing, so the guidance stays useful as the SDK evolves without needing every new adapter or option copied into the skill.

Development

bun install
bun run check-types
bun test
bun run build

Releases

Releases use Changesets, Depot-backed GitHub Actions runners, npm, and the repo-local Homebrew formula. See AGENTS.md.

Do not run the docs dev server unless you actually want a local preview:

bun run dev

Available Scripts

• bun run build: build all packages and apps
• bun run check-types: check TypeScript types across the workspace
• bun test: run package tests
• bun run check: Run Oxlint and Oxfmt
• bun run dev: start the docs dev server through Turbo