@tiptap-pro/extension-export-doc changelog

Changelog for @tiptap-pro/extension-export-doc

0.7.1

Add a region option to use the US conversion API (api-us.tiptap.dev). A set endpoint still wins. options.endpoint now reads undefined unless you set it.

Fix browser bundlers such as Turbopack failing to build these packages because their ESM output imported node:module.
PDF, DOC, ODT and EPUB exports now use the styleOverrides and customNodes set on ExportDocx and report DOCX errors, and exportDocx command options are optional in TypeScript.
The DOCX, PDF, DOC, ODT, EPUB and Markdown conversion extensions now log a development warning when ConvertKit is missing from the editor, so you know why converted documents may lose formatting.
Updated dependencies
Updated dependencies
- @tiptap-pro/extension-convert-kit@0.13.0

Forward the pageColor option through ExportPdf, ExportDoc, and ExportOdt to the DOCX intermediate so it is honored when exporting through these formats. See @tiptap-pro/extension-export-docx for accepted values and behavior.

Add header and footer properties to the pageMargins option, controlling the distance from the page edge to the header/footer. When the Pages extension is configured, these values are auto-derived from headerTopMargin and footerBottomMargin; caller-provided values always take precedence.

For extension-export-pdf, extension-export-doc, and extension-export-odt, full end-to-end support requires the Tiptap convert service to be on a version that accepts the new pageMargins.header/footer fields and ships an updated @tiptap-pro/extension-export-docx.

Custom node conversion is now supported for PDF, DOC, ODT, and EPUB exports. To automatically opt-in to this feature the ExportDocx extension needs to be present in your editor extensions configuration, otherwise the customNodes configuration will be ignored as it relies on the ExportDocx conversion service.