Just use MJML (https://github.com/mjmlio/mjml) or mrml (https://github.com/jdrouet/mrml). It solves the real problems with building emails without introducing useless abstractions like JSX.
If 1 does the job equally well, you should choose 1.
In fact, MJML can be used with any templating solution, so if your system already uses JSX, JSX doesn't add indirection, and you should use it.
But if your system is not, adding JSX on top has just prevents you from hacking a shell scripts that generates the email in a few lines, generating the email from whatever backend you use, or just writing the template in a free form file without anything to install.
You gain complexity, you loose flexibility.
> MJML can be used with any templating solution
Wouldn't that add complexity where JSX has less? Why use 2 systems (MJML + [templating]) when you can get away with 1 (JSX)?
> adding JSX on top has just prevents you from hacking a shell scripts
As far as I understand both are npm libraries so I can't see how one allows this where the other doesn't? Surely their application is the same usage pattern?
And libraries like mjml-react make it really easy.
Anyways it seems that Wix is no longer maintaining the project and Faire has taken it on: https://github.com/Faire/mjml-react
- proper i18n with any react i18n library
- js to create complicated emails
- nicer component reuse story.
- syntax highlighting and completion when used with Typescript
- can be integrated with other nice js tools like Storybook for seeing all emails in one place and play with their props.
How is that useless?
The discourse would be much less boring.
I once worked with a guy who kept looking over my shoulder and saying 'just use binary'. Nice guy, but they had to let him go.