Snarkdown VS ShowdownJS

Analyzing these dependencies, I found that some of them could be reduced or replaced. For example, jquery-ui is used for autocompletion and reordering. All additional widgets provided by jquery-ui (e.g. sliders, datepickers) are dead weight and can be excluded from the final bundle. Another example is marked, which was used to render the changelog. However, the changelog has a very simple structure and does not... Source: about 3 years ago

So you're going to need a Markdown parser that produces HTML. But there's a question of where is the data coming from and where you you want to process it? If it's going to be all on the frontend like a text editor, use a JS library for it (a quick google search produces ShowdownJS). Source: over 1 year ago

Previously, I was required to implement the markdown support manually which meant that the use of public libraries was prohibited. My tool could only support limited styling elements such as header1, header2, links, bold and italics, but now I can finally let my tool have a full markdown support by using Showdown. - Source: dev.to / over 1 year ago

The first two ages are very heavy on content so I decided to use markdown and tailwind’s typography plugin for styling. I also used showdown to fetch the markdown and turn it into HTML. The code for the above can be found on the site’s GitHub repository. - Source: dev.to / over 1 year ago

I'm using https://github.com/showdownjs/showdown for the core rendering-markdown functionality, with a bunch of additional listeners etc on top of it to fit it into the notion-style UX! Hope that helps :). Source: over 1 year ago

It looks like it uses showdown as the engine. Source: almost 2 years ago