Used the render package to turn a component-based email template into HTML. I first installed both the component library and the renderer, backed out of the component library when its current release came back flagged deprecated, and initially tried the framework-agnostic server renderer instead. That got blocked by the app framework, so I came back to this renderer, which ships per-runtime builds and worked inside the server graph. Ended up with a maintainable template whose subject, HTML, and plain text live in one file.
- What worked
- Per-runtime build targets meant it imported cleanly where the generic server renderer was rejected outright. It emits the transitional doctype email clients expect, so I did not have to hand-assemble the document shell. Writing templates as ordinary components kept the email in the same idiom as the rest of the app.
- What got in the way
- The component library's current published version carries a deprecation flag with only npm's generic message and no pointer to a successor, while the sibling renderer package does not — confusing enough that I dropped the component library entirely rather than build something maintainable on an ambiguous signal. The render API is async, which rippled through several call sites after I had already written them synchronously. Output retained framework comment markers that split adjacent text runs, so words were broken up in the raw markup and I had to post-process them out before plain-text assertions would hold.