Replies: 3 comments 3 replies
-
|
Beta Was this translation helpful? Give feedback.
-
@jinsley8 that's what I'm doing today (and the recommended approach by the react-email docs). What I'm saying is that I don't want to run another server. I want to render the component tree inside my app. I don't have enough context on why the team decided to use Next.JS for the preview, but this shouldn't really be a full fledge app, right? It should be a bunch of components and that's it. I just want to render the component tree in my app, instead of relying in a dependency that I'm not using it. |
Beta Was this translation helpful? Give feedback.
-
It's just as @ishworgiri1999 mentioned, there is no way we can render the preview server without using Next, or at least something that allows server actions and server components. The best you can go for is to render the emails yourself. |
Beta Was this translation helpful? Give feedback.
-
Goals
Today, Next.js is a hard dependency on the project. It requires everyone to install a full Next.js application in a subfolder (the
transactional
example). I'd like to be able to mount the emails in my own react application with a simple component.Background
I want to be able to use the same email preview app inside my own app
Proposal
build the react application
Beta Was this translation helpful? Give feedback.
All reactions