feat: add batch specific email options type to reflect API limitations

[titouv]

Summary

• Exclude attachments and scheduledAt from CreateBatchEmailOptions type to reflect batch API limitations
• Add new CreateBatchEmailOptions type using Omit<CreateEmailOptions, 'attachments' | 'scheduledAt'>

These fields are not supported by the batch API as documented at https://resend.com/docs/dashboard/emails/batch-sending#limitations

Objective

This tries to solve a problem I encountered where the types allowed an attachments array value, but no attachments could be sent via the Batch API and the "issue" was just ignored misleading the developper.

This provides compile-time errors when users attempt to use unsupported features with batch sending.

---

Summary by cubic

Align batch email types with API limitations by excluding attachments and scheduledAt. Adds CreateBatchEmailOptions and updates CreateBatchOptions to use it, so unsupported fields cause compile-time errors.

^{Written for commit 5e3f2e5. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 1 file

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/resend/resend-node/resend@801

commit: 5e3f2e5