-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to render in a next.js server action #40
Comments
#36 will resolve this. |
Please try the latest version of |
Looks good. (https://stackblitz.com/edit/stackblitz-starters-f4gt7r?file=package.json) So the solution for now would be to install all components individually and to not use the tbh, it was unexpected that the |
thought about changing that too, but went with it as it is to make it easy for people to switch from react-render |
all v2.1.0 published Please give this a test and let us know how it works out |
No more error message (https://stackblitz.com/edit/stackblitz-starters-83gr6n?file=app%2Faction.ts) The rendering output also looks good. Do you plan to publish releases here with change logs? I would subscribe to them. |
possibly in the future, but for now we're just tagging and updating the changelog. |
@jsxp-email/cli
Version?: 1.0.14Expected Behavior
Should be able to render in a server action.
Actual Behavior
Additional Information
This is related to
resend/react-email#871
vercel/next.js#43810 (probably includes the fix)
It has been fixed in react-email already because I was able to render in a server action using their package before.
The text was updated successfully, but these errors were encountered: