Type-Safe Email Events for React Teams

Short summary

The author advocates treating transactional email payloads as typed product events shared across React, API, and worker layers using a single schema (e.g., Zod). This prevents silent drift when fields are renamed or made optional, causing blank emails in production. Each email action gets its own small schema module with required fields, optional fields, and a version number, creating a clean fail point when any layer diverges.

• •Treat email payloads as typed events, not loose JSON blobs
• •Share one Zod schema across React, API, and worker for validation
• •Version each event (e.g., account.invite.sent.v1) to make schema changes intentional

Generated with AI, which can make mistakes.