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

I've added a few more test cases which highlight some failures with double characters, going to take a look into that.

I think we should go ahead and split markdown into two separate packages:

• @lexical/markdown-shortcuts that will only handle as-you-type conversion
• @lexical/commonmark or @lexical/remark for import/export with external library dependency. Attempting to do import/export with regexp will never be 100% precise, and proper tokenization is the only way (although at cost of code size)

I think we should go ahead and split markdown into two separate packages:

• @lexical/markdown-shortcuts that will only handle as-you-type conversion
• @lexical/commonmark or @lexical/remark for import/export with external library dependency. Attempting to do import/export with regexp will never be 100% precise, and proper tokenization is the only way (although at cost of code size)

I wonder if we can keep a single package, just expose different utilities from it. I understand the idea of not having the large 3P dependencies, but structured properly those should be tree-shaken out for anyone not using exports that depend on them.

I think we should go ahead and split markdown into two separate packages:

@lexical/markdown-shortcuts that will only handle as-you-type conversion
@lexical/commonmark or @lexical/remark for import/export with external library dependency. Attempting to do import/export with regexp will never be 100% precise, and proper tokenization is the only way (although at cost of code size)

FWIW that's pretty much what we ended up doing in our editor because regex based matching wasn't reliable or complete enough.

On plain text paste events we first run the text through markdown-it with the same setup/plug-ins we use elsewhere then effectively "paste" the resulting HTML so that it's run through all of our node's importDOM methods. Felt like that way we can keep the importDOM methods as a more central place for handling conversion too.

FYI @fantactuka I'm no longer working this PR as I've fully switched over to lexical-remark. Feel free to close it.