• Looks like it crashes for an empty file
• Crashes for a file with only the YAML frontmatter and no other content
• Same for JSON
• Probably add a test for re-running on a TOC'ed frontmatter file?
• Test case with processAll?
• The startsWith/endsWith check on .raw breaks if the closing delimiter has trailing whitespace, e.g. "+++\ntitle: test\n+++ \n"

two small notes, looks just about ready!

Nice! It looks like there's one regression worth addressing here. The frontmatter doc/body split in check() above assumes the
closing delimiter is followed by exactly one blank line:

var pos = md.indexOf(tag,3) + 3 + 2 * eol.length;

With anything other than one blank line, pos is wrong (here, 0 blank lines drags the first char of the next line into the doc segment).

Separately, md.substring(0, 3) matches any 3-char prefix in ['---', ';;;', '+++'], so a horizontal-rule "---" at the top of a doc is misclassified as frontmatter and falls into the same broken path. Both should round-trip once the helper scans for the next non-blank line after a verified closing tag.

A couple sample checks, which both fail right now:

// 0 blank lines after the closing delimiter
check(
  [ '---'
  , 'title: Yaml'
  , '---'
  , '# H'
  , 'body'
  ].join('\n')
, [ '**Table of Contents**  *generated with [DocToc](https://github.com/thlorenz/doctoc)*\n\n'
  , '- [H](#h)\n\n\n'
  ].join('')
)

// "---" at the top is a horizontal rule, not frontmatter — helper false-positive
check(
  [ '---'
  , ''
  , '# Real Heading'
  , 'body'
  ].join('\n')
, [ '**Table of Contents**  *generated with [DocToc](https://github.com/thlorenz/doctoc)*\n\n'
  , '- [Real Heading](#real-heading)\n\n\n'
  ].join('')
)

I was inclined to let it be a follow-up, as I think it's maybe unlikely for docs to have a leading --- without it being frontmatter... But it would be quite unfortunate if they did. Let's do one more round and address this as in scope to the PR.

Pull request overview

Adds support for documents that start with front matter by ensuring the generated TOC is inserted after the front matter region (keeping the front matter block valid), and expands the test suite to cover YAML/TOML/JSON-style delimiters.

Changes:

• Adjust TOC insertion and header scanning start positions to account for detected front matter.
• Add a dedicated front matter test suite and fixtures (yaml/toml/json/invalid/blank/existing-TOC cases).
• Update the shared transform test helper to build expected docs with TOC placed after front matter.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 3 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

almost there, I think there's another edge case where a stray \r\n can lurk:

test('\ngiven a file with CRLF line endings and yaml frontmatter', function (t) {
  var eol = '\r\n';
  var content = ['---', 'title: Yaml Front Matter', '---', '', '# Heading', '', 'Your regular Markdown content follows...', ''].join(eol);
  var res = transform(content);

  t.same(
      res.data
    , [ '---',
        'title: Yaml Front Matter',
        '---',
        '',
        '<!-- START doctoc generated TOC please keep comment here to allow auto update -->',
        '<!-- DON\'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->',
        '**Table of Contents**  *generated with [DocToc](https://github.com/thlorenz/doctoc)*',
        '',
        '- [Heading](#heading)',
        '',
        '<!-- END doctoc generated TOC please keep comment here to allow auto update -->',
        '',
        '# Heading',
        '',
        'Your regular Markdown content follows...',
        '' ].join(eol)
    , 'generates correct toc preserving CRLF line endings with frontmatter'
  )

  t.end()
})