Resend & React Email Patterns FAQs

Question 1

Why must I await the render() function in this skill?

Accepted Answer

In React Email 5.0 and later, the render() function returns a Promise. Failing to await it will cause the email body to be sent as the string '[object Promise]' instead of the actual HTML content.

Question 2

How does this skill ensure CAN-SPAM compliance?

Accepted Answer

The skill provides patterns for generating signed unsubscribe tokens and mandatory inclusion of unsubscribe links in all non-transactional/marketing emails, which is a legal requirement.

Question 3

How many recipients does the Resend batch API support?

Accepted Answer

The batch API allows you to send emails to between 2 and 100 recipients in a single request. Note that batch sending does not currently support attachments or scheduled delivery.

Question 4

Is it safe to use Resend API keys on the frontend?

Accepted Answer

No. You must always use server-side sending for all emails. Exposing your RESEND_API_KEY to the client-side code is a critical security vulnerability that allows unauthorized parties to send emails using your account.

Question 5

Can I use Tailwind CSS for styling my email templates?

Accepted Answer

Yes, the skill supports Tailwind CSS through the @react-email/tailwind wrapper. It includes guidance on using Tailwind 4 features compatible with React Email 5.0+.

Resend & React Email Patterns

Características Principales

Casos de Uso

Resend & React Email Patterns

Características Principales

Casos de Uso