b70aefd5cc
invoiceData.ts's generateInvoicePdf()/generateCorrectionInvoicePdf() now call renderInvoiceEInvoice()/renderCorrectionInvoiceEInvoice() instead of the plain PDF renderers — both are the single wrapper every caller already goes through (orderEmail.ts's checkout attachment, and the two on-demand /invoice and /correction-invoice download routes), so this one change switches all three. Buffer.from() wraps the library's Uint8Array return value — every downstream consumer already expects a Buffer, unchanged. Imports from "@einfach-produktiv/invoicing/einvoice" (a new subpath, not the package's main entry) — @e-invoice-eu/core pulls in Node-only dependencies that broke the client bundle when reachable from the main entry, which a Client Component also imports transitively (Live Preview). See that package's own commit for the fix. Existing failure-handling is unchanged and covers this: a PDF-generation error still doesn't block the confirmation email, it just sends without the attachment and alerts admin (see orderEmail.ts) — same safety net that already existed for the plain-PDF path. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>