gray-matter

A simple to use and extend front matter library. Supports parsing and extracting YAML, JSON, TOML or Coffee Front-Matter, with options to set custom delimiters.

Used by assemble, verb, and thousands of other projects!

v0.5.0 has breaking changes!

  • YAML is now parsed using the .safeLoad() method from js-yaml.

  • To parse coffee, CSON or javascript front matter, you must set options.eval to true.

  • stringify() has been renamed to toJSON()

  • stringifyYAML() has been renamed to toYAML()

Highlights

  • Reliable and battle-tested.

  • Will extract and parse:

  • Easy to add additional parsers! pull requests welcome!

TOC

Install

Install with npm

npm i gray-matter --save

Install with bower

bower install gray-matter --save

Usage

var matter = require('gray-matter');
console.log(matter('---\ntitle: foo\n---\nbar');
//=> {data: {title: 'foo'}, content: 'bar', orig: '---\ntitle: foo\n---\nbar'}

API

matter

Expects a string and returns and object:

  • str {String}: The string to parse

  • options {Object}: Object of options

  • returns {Object} file: Object with the following properties. 

matter('---\ntitle: Blog\n---\nThis is content.');

Returns:

{
  "data": {"title": "Blog"},
  "content": "This is content.",
  "original": "---\ntitle: Blog\n---\nThis is content."
}

.read

Read a file then pass the string and options to matter() for parsing:

  • filepath {String}

  • options {Object}

  • returns {Object} file: Same object as matter(), with an additional path property 

matter.read('file.md');

Returns something like:

{
  "data": {"title": "Blog"},
  "content": "This is content.",
  "original": "---\ntitle: Blog\n---\nThis is content."
}

.exists

Return true if front-matter exists.

  • str {String}: The string to parse

  • options {Object}: Options to pass to matter()

  • returns {Boolean} true: or false 

matter.exists(str);

.extend

Extend and stringify YAML front matter. Takes an object as the second parameter, and returns either the extended, stringified object (YAML), or if no front matter is found an empty string is returned.

  • str {String}: The string to parse

  • obj {Object}: The object to use to extend the front matter.

  • returns {String}: String with extended YAML front matter. 

matter.extend(str, obj);

.reconstruct

A convenience wrapper around the matter() and matter.extend() methods.

  • str {String}: The string to parse

  • obj {Object}: The object to use to extend the front matter.

  • returns {String}: Original string with extended front matter.

Extends YAML front matter, then re-assembles front matter with the content of the file.

matter.reconstruct(str, obj);

.toJSON

  • str {String}

  • options {Object}

  • returns {Object}: Parsed front matter as JSON.

Convenience wrapper around the matter(str).data() method.

.toYAML

  • str {String}

  • options {Object}

  • returns {String}: Stringified YAML.

Stringify parsed front matter back to YAML.

Options

All methods will accept an options object to be passed as a second parameter

options.eval

Type: Boolean

Default: false

Evaluate coffee-script, CSON or JavaScript in front-matter. If you aren't aware of the dangers, google is your friend.

options.lang

Type: String

Default: yaml

The parser to use on the extracted front matter. Valid options include:

  • yaml

  • json

  • coffee

  • cson

  • toml

  • js|javascript

options.delims

Type: Object

Default: {delims: ['---', '---']}

Open and close delimiters can be passed in as an array of strings. Example:

matter.read('file.md', {delims: ['~~~', '~~~']});

You may also pass an array of arrays, allowing multiple alternate delimiters to be used. Example:

{
  delims: [
    ['---', '~~~'], ['---', '~~~']
  ]
}

Note that passing multiple delimiters will yield unpredictable results, it is recommended that you use this option only for testing purposes.

options.autodetect

Type: Boolean

Default: undefined

Attempts to automatically register a language that is specified after the first code boundary (delimiter).

Usage Example:

--- coffee
user = 'jonschlinkert'
reverse = (src) ->
  src.split('').reverse().join('')
---

{%= user %}
{%= reverse(user) %}

Examples

Let's say our page, foo.html contains

---
title: YAML Front matter
description: This is a page
---
<h1>{{title}}</h1>

then running the following in the command line:

console.log(matter('foo.html'));

returns

{
  "data": {
    "title": "YAML Front matter",
    "description": "This is a page"
  },
  "content": "<h1>{{title}}</h1>",
  "original": "---\ntitle: YAML Front matter\n---\n<h1>{{title}}</h1>"
}

and

console.log(matter('foo.html').data);

returns

{"title": "YAML Front matter", "description": "This is a page"}

.extend

Given this page:

---
title: Gray Matter
---
Hooray!

and this config:

var file = require('fs').readFileSync('file.md', 'utf8');
var obj = {
  description: 'A simple to use front matter lib';
};
matter.extend(file, obj);

the result would be:

---
title: Gray Matter
description: A simple to use front matter lib
---
Hooray!

Why?

Why another YAML Front Matter library?

Because other libraries we tried failed to meet our requirements with Assemble. Some most of the libraries met most of the requirements, but none had all of them. Here are the most important:

  • Be usable, if not simple

  • Allow custom delimiters

  • Use a dependable and well-supported library for parsing YAML and other languages

  • Don't fail when no content exists

  • Don't fail when no front matter exists

  • Have no problem reading YAML files directly

  • Have no problem with complex content, including fenced code blocks that contain examples of YAML front matter. Other parsers fail on this.

  • Should return an object that contains the parsed YAML front matter and content, as well as the "original" content.

Authors

Jon Schlinkert

License

Copyright (c) 2014 Jon Schlinkert, contributors. Released under the MIT license

This file was generated by verb-cli on October 24, 2014.

Previous{%= name %} {%= badge("fury") %}Nexttest

Last updated