marked

How does Satteri compare to a standard library like marked (https://github.com/markedjs/marked)?

Another contestant in this realm is Bright[1]. It runs entirely on the server and doesn't increase bundle size as seen here[2]. Regarding parsing speed tree-sitter is without a doubt performant since it is written in Rust, but I don't have any problems "parsing on every keystroke" with a setup containing Marked[3], highlight.js[4] and a sanitizer. I did however experience performance issues with other Markdown parser libraries than Marked. [1]: https://bright.codehike.org/ [2]: https://aihelperbot.com/test-suite [3]: https://github.com/markedjs/marked [4]: https://highlightjs.org/

I once made a very crude and simple TiddlyWiki work-alike I called "HulloWurld" https://github.com/calroc/HulloWurld It's 143 KB, but it includes copies of Knockout, Underscore, Zepto, and the "Marked" markdown parser... ¯\_(ツ)_/¯ ( Good stuff BTW: http://knockoutjs.com/ http://underscorejs.org/ https://zeptojs.com/ https://github.com/chjj/marked ) Probably the only interesting bit is the code to save the page: https://github.com/calroc/HulloWurld/blob/1f88da21081a73469a... But I didn't figure that out, I got it from stackoverflow: https://stackoverflow.com/questions/27177661/save-html-local... It has two CSS styles! Eh? ( https://developer.mozilla.org/en-US/docs/Web/CSS/Alternative... ) Live demo: https://calroc.github.io/HulloWurld/Hullo.html

I think https://github.com/markedjs/marked would be one of the more popular libraries in this category

I've used marked for years, and it doesn't make any network calls. In fact, it looks like it does tons of regex. https://github.com/markedjs/marked

This comes on top of Marked[1], so it is a dependency. Use with care. From my experience any of the trio, Marked[1], Showdown[2] and Markdown-it[3], can be configured to just do it themselves. As a side note, I built a markdown editor once that works client side and resides inside "real static" html. Demo for the interested: http://public.docs.xstatic.site.s3-website-us-west-1.amazona... [1] https://github.com/markedjs/marked [2] https://github.com/showdownjs/showdown [3] https://github.com/markdown-it/markdown-it

Hey Adam, you should probably avoid marked.js. It suffers from a number of security issues [1] and it's unmaintained (or at least the maintainer is AWOL and without him new releases can't be tagged). Markdown-it is probably a good alternative. [2] [1]https://github.com/chjj/marked/issues?utf8=%E2%9C%93&q=is%3A... [2]https://github.com/markdown-it/markdown-it

For those wondering which of the thousand bespoke dialects of Markdown this speaks, this project uses marked.js: https://github.com/chjj/marked

Great work! Always happy to see people working towards a WYSIWYG editor for Markdown. I did a similar project¹, with strong focus on editing math, inline, and “real time” wysiwyg. It failed. The problem is that most such approaches treat Markdown as _code_ instead of _text_, and inevitably mistake syntax highlighting for semantic, text-driven styling (as if one would style nouns, verbs, adjectives, instead of <h1>, <p>, <em>, etc.). Thus they use a code editor such as CodeMirror (like this one does, too). And then you must style `.cm-` syntax markers instead of the eventual (html) nodes that would be the output of a real Markdown parser. Which makes it impossible to just throw in any arbitrary html5 css-stylesheet. Which is imho the whole point of wysiwyg Markdown editing. What you’d really want instead is true Markdown parsing, which nor

We use marked - https://github.com/chjj/marked - with some slight modifications.

I'm currently using marked, which has worked wonderfully: https://github.com/chjj/marked And will look into pandoc, thank you!

We started with a server side Markdown parser, but switch to a JavaScript parser (https://github.com/chjj/marked). Really there is no reason to do this work on the server.

this looks cool and super easy to add bidirectional HTML <> markdown support similar to the demo i did for redactor-js here: http://leeoniya.github.io/redactor-js/ using https://github.com/leeoniya/reMarked.js and https://github.com/chjj/marked may just have to do this after work today if no one gets to it first.

If it's referring to what I think it is, part of this is my fault and I feel I should give a post-mortem as well. There was a problem with marked (the markdown parser npmjs.org uses for READMEs) which allowed users to provide `javascript:` pseudo-protocol links even when the `sanitize` option was enabled. It was fixed[1] with marked v0.3.1 on jan. 31st. It looks like npm-www started using marked v0.3.1 on feb. 17th[2]. [1] https://github.com/chjj/marked/commit/904c71b7713979b01d5bc5... [2] https://github.com/npm/npm-www/commit/a1ed923870609b578fcde4... edit: On closer inspection it looks like it may have been a problem with the html sanitizer[3] it used as opposed to the marked `sanitize` option (which is not used at all). I guess my conscience is clear here at least. [3] https://github.com/npm/npm-www/blob/master/models/package.js...