feat: updating to use yaml

[sakulstra]

use yaml instead of js-yaml
as requested in #145

@jonschlinkert are you sure yaml is smaller than js-yaml (for some reason bundlephobia is broken for yaml and vscode showing bigger package size, might be wrong due to shaking though)

yaml seems to behave slightly different as you can see in the two failing tests.

[sakulstra]

@jonschlinkert with #148 applied tests are passing.

[jonschlinkert]

are you sure yaml is smaller than js-yaml (for some reason bundlephobia is broken for yaml and vscode showing bigger package size

I'm not at all sure about that lol. Thank you for doing this and for bringing it to my attention. I was initially under the impression that yaml would be smaller, since js-yaml was massively bloated the last time I checked. They included all of their tests, test fixtures, browser code, etc. in the published package. Now that you have seen both, what is your recommendation?

edit: and also, thank you for taking the time to do this, and apologies for making you jump through hoops. I promise we'll get this merged and published as soon as we settle on which library to use.

[sakulstra]

Would in fact go with yaml - seems more solid to me.

[sakulstra]

@jonschlinkert any chance of getting this merged? 😅

[sakulstra]

@jonschlinkert ping 😅

[sakulstra]

@jonschlinkert 😿 - quite a lot of ppl are using this library (1M downloads per week). Would be really good if this could be merged anytime soon.

[sakulstra]

@jonschlinkert ping on this, let me know if anything prevents merging.

[benmccann]

for some reason bundlephobia is broken for yaml

It no longer is. It shows yaml at 102.6 kB and js-yaml at 39 kB.

[pedzed]

@sakulstra Thank you for your contributions.

@jonschlinkert Understandably you may have had to make other priorities. Would you be so kind to make @sakulstra a maintainer of this project? This nice library needs to keep up with the time.

I am surprised that there is no TypeScript support (#105, #107, #181 and others).

[sakulstra]

@pedzed Thanks, but I have no interest in maintaining this project at this point.
Eventually we only need a very small portion of it's capabilities, so we have sth like:

import yaml from "js-yaml";

/**
 * Simple frontmatter parser using js-yaml
 * Extracts YAML frontmatter from markdown content
 */
export function parseFrontmatterMd(content: string): {
  data: Record<string, any>;
  content: string;
} {
  const frontmatterRegex = /^---\s*\n([\s\S]*?)\n---\s*\n?([\s\S]*)$/;
  const match = content.match(frontmatterRegex);

  if (!match) {
    return { data: {}, content };
  }

  const [, frontmatter, body] = match;
  const data = yaml.load(frontmatter) as Record<string, any>;

  return { data, content: body };
}

which covers all our needs.