@unlayer/react-elements 0.1.18 → 0.1.19

package/README.md

@@ -331,7 +331,12 @@ The document shell matches the mode: `<Email>` gets the XHTML transitional docty
 - `title` — document `<title>`
 - `fonts` — web-font stylesheet URLs to load via `<link>` tags, e.g. `[{ url: "https://fonts.googleapis.com/css2?family=Inter" }]`
 
-If your app owns the document shell (an existing page template, an ESP template, an iframe `srcdoc`), use `renderToHtmlParts` instead — it returns `{ head, body }` chunks for you to place yourself.
+If your app owns the document shell (an existing page template, an ESP template, an iframe `srcdoc`), use `renderToHtmlParts` instead — it returns `{ head, body }` plus the granular pieces (`css`, `js`, `tags`) for pipelines that need them separately, e.g. CSS inlining. This mirrors the editor's [chunk parameters](https://docs.unlayer.com/builder/latest/export-html#chunk-parameters) with two deliberate differences: `tags` is extra (components can contribute head tags, and reassembling from `css` + `js` alone would drop them), and there is no `fonts` chunk (Elements has no font registry — pass font stylesheet URLs via `renderToHtml`'s `fonts` option instead).
+
+```tsx
+const { head, body, css, js, tags } = renderToHtmlParts(<Email>...</Email>);
+// head = css/js/tags pre-assembled; css = raw stylesheet (no <style> wrapper)
+```
 
 ## Custom Tools
 

package/dist/index.cjs

@@ -1857,7 +1857,10 @@ function renderToHtmlParts(element, config) {
   }
   return {
     head: headParts.join("\n"),
-    body
+    body,
+    css,
+    js,
+    tags
   };
 }
 var schemaVersion = exporters.schemaVersion ?? 24;