fix: to support @react-email/render exports across versions in templates

[Shubhdeep12]

• @react-email/render dropped renderAsync in v2.0.0.

---

Summary by cubic

Adds a shared render helper that works with @react-email/render v1 and v2 by preferring render and falling back to renderAsync. Uses it in Templates and Emails with clearer errors.

• Bug Fixes
  • Add render helper that selects render or renderAsync and throws actionable errors.
  • Use helper in Templates and Emails; remove dynamic imports and cached renderer.
  • Add tests for helper behavior; update template tests to mock render.

^{Written for commit b05636e. Summary will update on new commits.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/resend@863

commit: 38eec3a

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

[gabrielmfern]

this should use

resend-node/src/render.ts

Lines 1 to 6 in d16e477

	export async function render(node: React.ReactNode) {
	let render: typeof import('@react-email/render').render;
	try {
	({ render } = await import('@react-email/render'));
	} catch {
	throw new Error(

[Shubhdeep12]

yeah, i thought earlier, since it's a peer dep, we wanted to give support for renderAsync.

thanks for the review, made the changes.

[gabrielmfern]

that's valid, but it should be done in that render function and reused

[Shubhdeep12]

i removed it in the last commit, lemme add the support of renderAsync back
and to render.ts that the right place

[gabrielmfern]

I don't think this cast is required, is it?

[Shubhdeep12]

yeah we can remove it, especially as we are narrowing the scope here with ReactElement.
lemme remove it and from other places as well.