@frontmail/emailjs-compat

Drop-in replacement for @emailjs/browser, backed by Frontmail. Same exports (init, send, sendForm, EmailJSResponseStatus, default export) and call signatures – migrating means changing the import and using your Frontmail ids.

- import emailjs from '@emailjs/browser';
+ import emailjs from '@frontmail/emailjs-compat';

  emailjs.init({ publicKey: 'pk_…' });
  await emailjs.send('svc_…', 'tpl_…', { name: 'Jan' });
  await emailjs.sendForm('svc_…', 'tpl_…', '#contact-form');

CDN: <script src="https://cdn.jsdelivr.net/npm/@frontmail/emailjs-compat/dist/emailjs-compat.umd.js"></script> exposes the same emailjs global.

Behaviour

• init(options | publicKey, origin = 'https://api.frontmail.dev'); options: publicKey (or legacy user_id), accessToken (private key, server only), blockHeadless, blockList, limitRate, storageProvider. Per-call options (4th argument) override init.
• Requests go to the EmailJS-compatible aliases /api/v1.0/email/send and /api/v1.0/email/send-form.
• Success resolves EmailJSResponseStatus { status: 200, text: 'OK' } plus Frontmail extras messageId, deliveryStatus (queued | held) and statusToken.
• Failures reject with EmailJSResponseStatus { status, text } (and error, the underlying FrontmailError): API errors keep their HTTP status and message, network errors are 0 'Network Error', blockHeadless → 451, blockList → 403, limitRate → 429.
• On top of EmailJS you get automatic retries with idempotency keys and the hold queue: when credits run out, emails are accepted (deliveryStatus: 'held') instead of being dropped.

For new code prefer @frontmail/browser, which exposes typed errors and statuses directly.

MIT