front-matter VS marked

To set our metadata dynamically, we also imported the front-matter dependency.

front-matter parser

What we want is for our editor to take the combination of front-matter data and markup, then be able to extract the two before storing that data separately somewhere. We'll be using the front-matter module to extract the data we need from the text editor content.

Vrite SDK provides a few built-in input and output transformers. These are functions, with standardized signatures to process the content from and into Vrite. In this case, gfmInputTransformer is essentially a GitHub Flavored Markdown parser, using Marked.js under the hood.

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/

To handle pasting block Markdown content like this, I had to tap into ProseMirror and implement a custom mechanism (though somewhat based on TipTap’s paste rules), detecting starting and ending points of the blocks and parsing them with Marked.js.

Again, with streaming enabled, you’ll now receive new tokens as soon as they’re available. Given that OpenAI’s API uses Markdown in its response format, a full message will need to be put together from the incoming tokens and parsed to HTML, as accepted by the replaceContent function. For this purpose, I’ve used the Marked.js parser.

Eleventy can take an .md file and output a .html but if you want to go as vanilla as possible you can just use a module like marked to do that.

Once you have the article data, you’ll likely have to process its body_markdown to a format required by your website, like HTML. There are many tools you can do this with — here’s an example using Marked.js:

While changeset still lacks some features like a unified changelog for all the package, this can be handled with some scripts. Using for example marked one could set up some parsing to create a unified changelog for the whole system.

did you look at the marked parser? (https://github.com/markedjs/marked) I'm using it for an upcoming plugin I'm working on

I used marked.js to build my blog. I use it as both an in browser editing tool and to compile markdown from a database on the server. It's certainly not as advanced as ByteMD or Milkdown, but it does have some extensions to bridge a few of the gaps.

Markdown isn't really standardised, but that's understandable wanting to use it if not all clients are web-based. If you only want to display the result and not have a rich editor, you could look into something simpler like Marked.