Two different emphasis are recognized as a single one in a paragraph node

[StanleySathler]

Thank you for the amazing work, guys! 🌟

Describe the bug
Let's suppose the following paragraph:

Before explaining about Promises, we should understand what is *async programming*. But, before, let's explain *synchronous programming* in a general context.

Before explaining about Promises, we should understand what is is consumed correctly.

The Lexer then calls the method Tokenizer.em() which then evaluates the set of em rules against the text.

But the last rule (/^\*([^\s*"<\[][\s\S]*[^\s])\*(?!\*)/) matches async programming* . But, before, let's explain *synchronous programming

Expected behavior
I expected to have matched only async programming.

To Reproduce
Just try to parse:

Before explaining about Promises, we should understand what is *async programming*. But, before, let's explain *synchronous programming* in a general context.

Demo

1. Marked Demo
2. CommonMark Demo

Version: 1.0.0

[rikedyp]

Just commenting to say I've bumped into this issue as well. Seems to do with * followed by punctuation as well?

Marked Demo

[calculuschild]

I have a PR #1686 that should fix this kind of issue but it's still waiting on feedback from the maintainers.

[calculuschild]

Can confirm this is fixed now.

[UziTech]

Should be fixed with marked v1.1.1 🎉