@tiby.eth Have you considered extending our parse-server-api-mail-adapter with a new payload converter? It’s our universal adapter that supports a variety of email service providers, with built-in features like templates and localization. I guess it could also be slimmer, as you are importing the resend package, which probably wouldn’t be necessary if you directly used the Resend REST API with our mail adapter and a payload converter.
Hi, no because I didn’t know about it. But the thing with this one is I need to have the template in html or in my case I like the fact that I only have email as react component.
Our API adapter supports HTML templates, and is also fully integrated with Parse Server to make the user object, and custom placeholder fields accessible within the templates. The advantage is that since it’s our official adapter for Parse Server, we run the CI and keep maintaining it.
All that’s needed for Resend seems to be to add a very lightweight (few lines of code) payload converter. The Resend npm package would not be added to the adapter but the adapter would relay your payload to it. Whatever payload you use (HTML, React code, etc) should work. We intentionally designed the adapter to be that flexible. Maybe take a look at how the existing payload converters work to get a better idea.
Yes, that’s right. If you look at the mailgun example in the README, you’d add the resend dependency in your own app, and just use the payload converter to feed it the right payload. It can be HTML, react, or whatever the resend package expects.