Two transports, one Worker-native workflow.

Use SMTP when you want TCP socket delivery, or Resend when you prefer the API-driven workflow. Both are built for Cloudflare Workers and share queue helpers.

@workermailer/smtp

SMTP

v0.1.4

SMTP client for Cloudflare Workers using TCP sockets, DSN, hooks, attachments, and queues.

TCP socket SMTP from Cloudflare Workers
Hooks, DSN, attachments, CID, and queues
Type-safe envelopes and auth modes

Library page Docs View on npm

@workermailer/resend

Resend

v0.1.0

Resend API client for Cloudflare Workers, aligned with @workermailer/smtp patterns.

Fetch-based Resend delivery for Workers
Shared envelope and queue patterns
Optional Cloudflare Queues helpers

Library page Docs View on npm

EmDash

Sandbox bundles ship with every library.

Both SMTP and Resend include EmDash-ready sandbox bundles in their repositories so you can wire providers without waiting on new API guesses.

If you are evaluating EmDash, start with the SMTP bundle for direct socket delivery, or use Resend when you prefer API-based sending. The libs page keeps links aligned with the current packages.