Which is Better Markdown Front Matter Parsers?
front-matter vs gray-matter vs yaml-front-matter
1 Year
front-mattergray-matteryaml-front-matterSimilar Packages:
What's Markdown Front Matter Parsers?

These libraries are designed to parse front matter from Markdown files, which is often used for metadata in static site generators and content management systems. Front matter is typically written in YAML or JSON format at the top of a Markdown file, allowing developers to define variables such as title, date, and layout. Each of these libraries offers unique features and capabilities for handling front matter, making them suitable for different use cases in web development.

NPM Package Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
front-matter2,159,283673-314 years agoMIT
gray-matter1,568,5543,951-664 years agoMIT
yaml-front-matter79,908192-204 years agoMIT
Feature Comparison: front-matter vs gray-matter vs yaml-front-matter

Supported Formats

  • front-matter: front-matter exclusively supports YAML format for front matter parsing, making it simple and effective for projects that only require YAML without any additional features.
  • gray-matter: gray-matter supports both YAML and JSON formats, providing flexibility for developers who may need to switch between formats or use different types of metadata in their Markdown files.
  • yaml-front-matter: yaml-front-matter is focused solely on YAML, ensuring robust parsing capabilities specifically tailored for YAML syntax, which can be beneficial for projects that leverage YAML's features.

Customization Options

  • front-matter: front-matter offers limited customization options, focusing on simplicity and ease of use, which may be sufficient for straightforward use cases but lacks advanced features.
  • gray-matter: gray-matter provides extensive customization options, allowing developers to define custom delimiters and ignore specific sections of front matter, making it adaptable to various project requirements.
  • yaml-front-matter: yaml-front-matter offers some customization capabilities, but its primary focus is on accurate YAML parsing rather than extensive configuration options.

Performance

  • front-matter: front-matter is optimized for performance, making it a suitable choice for projects where speed is critical, especially when processing a large number of Markdown files.
  • gray-matter: gray-matter balances performance with flexibility, ensuring that it remains efficient while providing additional features for parsing and customization.
  • yaml-front-matter: yaml-front-matter is efficient in parsing YAML but may not be as fast as front-matter due to its focus on YAML-specific features and parsing intricacies.

Ease of Use

  • front-matter: front-matter is designed for ease of use, with a straightforward API that allows developers to quickly integrate it into their projects without a steep learning curve.
  • gray-matter: gray-matter has a slightly steeper learning curve due to its additional features, but it remains user-friendly for those familiar with front matter concepts.
  • yaml-front-matter: yaml-front-matter is user-friendly for those who are comfortable with YAML, but may pose challenges for developers unfamiliar with YAML syntax.

Community and Support

  • front-matter: front-matter has a smaller community and fewer resources available compared to the others, which may limit support options for troubleshooting.
  • gray-matter: gray-matter has a larger community and more extensive documentation, providing better support and resources for developers.
  • yaml-front-matter: yaml-front-matter has a moderate community presence, offering some support but not as extensive as gray-matter.
How to Choose: front-matter vs gray-matter vs yaml-front-matter
  • front-matter: Choose front-matter if you need a lightweight and straightforward solution for parsing YAML front matter without additional dependencies. It's ideal for simple projects where minimalism and speed are priorities.
  • gray-matter: Opt for gray-matter if you require a more versatile parser that supports both YAML and JSON front matter, along with the ability to customize parsing behavior. It's suitable for projects that need flexibility and additional features such as ignoring front matter in specific contexts.
  • yaml-front-matter: Select yaml-front-matter if your primary focus is on YAML parsing and you want a library that integrates seamlessly with YAML-specific features. This package is best for projects heavily reliant on YAML syntax and structure.
README for front-matter

front-matter

build coverage npm github

Sauce Test Status

Extract meta data (front-matter) from documents.

This modules does not do any IO (file loading or reading), only extracting and parsing front matter from strings.

This concept that was originally introduced to me through the jekyll blogging system and is pretty useful where you want to be able to easily add meta-data to content without the need for a database. YAML is extracted from the the top of a file between matching separators of "---" or "= yaml =". It will also extract YAML between a separator and "...".

Install

With npm do:

npm install front-matter

Example

So you have a file example.md:

---
title: Just hack'n
description: Nothing to see here
---

This is some text about some stuff that happened sometime ago

NOTE: As of front-matter@2.0.0 valid front matter is considered to have the starting separator on the first line.

Then you can do this:

var fs = require('fs')
  , fm = require('front-matter')

fs.readFile('./example.md', 'utf8', function(err, data){
  if (err) throw err

  var content = fm(data)

  console.log(content)
})

And end up with an object like this:

{
    attributes: {
        title: 'Just hack\'n',
        description: 'Nothing to see here'
    },
    body: 'This is some text about some stuff that happened sometime ago',
    bodyBegin: 6,
    frontmatter: 'title: Just hack\'n\ndescription: Nothing to see here'
}

Methods

var fm = require('front-matter')

fm(string, { allowUnsafe: false })

Return a content object with two properties:

  • content.attributes contains the extracted yaml attributes in json form
  • content.body contains the string contents below the yaml separators
  • content.bodyBegin contains the line number the body contents begins at
  • content.frontmatter contains the original yaml string contents

NOTE: By default fm() uses ys-yaml's safeLoad unless you set allowUnsafe in the options object to true.

fm.test(string)

Check if a string contains a front matter header of "---" or "= yaml =". Primarily used internally but is useful outside of the module.

Returns true or false

    fm.test(string) #=> true || false

Contributing

front-matter is an OPEN Source Project so please help out by reporting bugs or forking and opening pull requests when possible.

standard

All code is linted/formatted using standard style, any non-conforming code can be automatically formatted using the the fmt make task: make fmt.

Maintainers

Contributors

This module is awesome because of all the folks who submitted pull requests:

CHANGELOG

3.0.0

  • CI only tests Node versions >= v6 (drops v4, and v5)

LICENSE (MIT)

Copyright (c) Jason Campbell ("Author")

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.