Which Markdown Parser?

[nelsonic]

We are currently using marked because it seemed like the better option at the time we were starting this project ...
But Mr. @alanshaw has opted for _remarkable_ in his project: https:/alanshaw/markdown-pdf

Which one should we be using and why? What makes one "better" than the other?
are there more options to consider or are these the two best ones...?

If anyone has time to do empirical research on this topic it would be incredibly useful! 👍

[alanshaw]

I swapped because for a long time marked was vulnerable and appeared abandoned.

https://david-dm.org/dwyl/adoro

[nelsonic]

Wow... that's a lot of RED ink _pixels_...
Ok. for now, we're switching to _remarkable_
and we can always re-visit this issue if anyone spots a performance, security or features issue with using it.

Thanks @alanshaw 👍

[des-des]

If we are trying to create amp HTML compliant pages (see issue #33) should this be done during or after the md-html conversion? Our current approach is to use remarkable to build html from the markdown. Then, either using the custom rules in remarkable and/or through another conversion make the html amp compliment before inserting it into our template.
Going to start down this route now, any thought appreciated!

[nelsonic]

@des-des as verbally discussed, your objective today should be to have a pipeline that converts
MD > HMTL and then Check AMP Compliance
Once you know what non-compliant html tags are generated by your Markdown Parser, you can write a transformer step from the HTML to AMP-HTML (TDD)