4 ms·

Exactly this. Said differently - how many devs out there are screaming "I really need to send transactional email via React", when most apps are sending it via

• nlh 3y ago
  Preface: I'm with you on this. But I think the targeting here is for a certain generation of companies where there is a very distinct backend/frontend split OR companies where everyone is a JavaScript dev (and the backend is Node). The backend folks send the email content and the frontend folks are responsible for building the presentation-layer stuff. The thinking here, I believe, is that those frontend guys do all their other work in React, so when they're given these transactional emails to build, they'd prefer to keep working in React. I think?
• ovao 3y ago
  I think you’re conflating terms (or possibly concepts) here. This isn’t about sending emails via React; this is about sending HTML emails generated from React components via a backend. The examples shown on the landing page are of Node.js, Next.js route handlers and Remix loader functions, the latter two being fancy abstractions over Lambda functions (or isolates). I agree that sending an email from React doesn’t make a lot of sense, but that’s not the target at which this is aiming.
• satvikpendem 3y ago
  Er, you can send the emails via whatever backend service you want. React merely acts as a templating language and when compiled down to HTML, you can then send the resultant file with Python, NodeJS, etc.