[lexical] Chore: Add export of DOMExportOutputMap from lexical

[Kingscliq]

Description

In the current setup, the DOMExportOutputMap type is not exported from the Lexical core, making it challenging for developers to define custom export configurations in the html property of CreateEditorArgs without re-creating this type from scratch. This process can lead to redundant code and a higher risk of type errors, particularly for configurations that customize DOM export logic.

This PR exports DOMExportOutputMap directly from the Lexical core, allowing developers to use this type immediately in any html.export configurations, which:

1. Reduces redundant type definitions.
2. Improves code readability and reusability.
3. Enhances type safety for custom DOM export setups.

Closes #6802

Test plan

Before

Developers needed to manually define DOMExportOutputMap, increasing the risk of type errors and inconsistencies in custom export configurations.

After

With DOMExportOutputMap now directly accessible from the Lexical core, developers can import and use the type immediately, resulting in cleaner and more robust custom export setups.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
lexical	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 7, 2024 5:22am
lexical-playground	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 7, 2024 5:22am

[github-actions]

size-limit report 📦

Path	Size
lexical - cjs	29.92 KB (0%)
lexical - esm	29.78 KB (0%)
@lexical/rich-text - cjs	38.57 KB (0%)
@lexical/rich-text - esm	31.63 KB (0%)
@lexical/plain-text - cjs	37.22 KB (0%)
@lexical/plain-text - esm	28.94 KB (0%)
@lexical/react - cjs	40.33 KB (0%)
@lexical/react - esm	33.06 KB (0%)