0.1.1 • Published 7 years ago
metalsmith-doctoc-jsdom v0.1.1
metalsmith-doctoc-jsdom
This metalsmith-doctoc (npmjs, github) plugin will use jsdom (npmjs, github) to read the heading tags from any HTML content. It will process fully specified HTML documents, or a mere tag soup (e.g. no html, head or body tags).
Installation
npm install metalsmith-doctoc-jsdom
Options object
This plugin will accept the following options object:
Options {
//- these are jsdom specific options:
// https://github.com/tmpvar/jsdom
//- this options object will be passed on to jsdom
jsdomOptions: {
//- will be returned by window.location, document.URL, ...
url: 'about:blank',
//- affects document.referrer
referrer: undefined,
//- affects document.contentType, and how a document is
// parsed (as HTML or XML).
//- must be a valid XML mime type
// https://mimesniff.spec.whatwg.org/#xml-mime-type
contentType: 'text/html',
//- affects navigator.userAgent, 'User-Agent' header
userAgent: 'jsdom/${jsdomVersion}',
//- enable to preserve the location info produced by the
// HTML parser; allows to query the location of an
// element inside the source content
//- negatively affects the performance
includeNodeLocations: false
},
//- used to select which method to use in order to extract
// modified content from jsdom; this will only happen if
// id values had to be generated.
//- must be one of: 'body', 'complete', 'auto'
//- 'body' - use this setting if file contents aren't fully
// specified documents. if they are and you use this setting,
// parts of your contents will be lost (i.e. no title, head
// or html tag).
//- 'complete' - use this setting if file contents are fully
// specified documents (i.e. have html, head, title tags).
// if file contents only hold inner tags (i.e. tag soup),
// then your actual content will receive additonal tags
// (html, head, body).
//- 'auto' - use this setting if your files hold mixed content.
// when this setting is used, jsdomOptions.includeNodeLocations
// will always be set to true to allow searching the body tag
// within the source content. if that tag was found, the
// 'complete' method will be selected; 'body' otherwise.
jsdomSerialization: 'complete',
//- $range = 'h$min-$max'
//- with $min and $max in [1,6] and ($min <= $max)
//- $min will replace hMin and $max will replace hMax
hRange: "h1-6",
//- an integer value in [1,6]
//- if hMin=X, then this plugin will
// ignore any heading tag <hN> if (N < X)
//- if (hMin == hMax == X), then this plugin will
// ignore any heading tag, but not <hX>
//- if (hMin > hMax), then all heading tags will be ignored!
hMin: 1,
//- an integer value in [1,6]
//- if hMax=X, then this plugin will
// ignore any heading tag <hN> if (N > X)
//- if (hMin == hMax == X), then this plugin will
// ignore any heading tag, but not <hX>
//- if (hMin > hMax), then all heading tags will be ignored!
hMax: 6,
//- $selector = /h[1-6](,\s*h[1-6])*/
//- a heading will only be taken into account, if it's tag
// can be found inside hSelector
//- if hRange is given, it will override hMin and hMax
//- if hMin or hMax are given, they will override hSelector
//- hSelector is what will be used to find the heading tags
hSelector: 'h1, h2, h3, h4, h5, h6',
//- use this value to specify a cheerio context in which to
// look for heading tags.
//- e.g. use '' to search the whole document
//- e.g. use '#id' to only search the element marked with the
// specified id value.
hContext: '',
//- string function(string)
//- this function will be used to calculate a missing id:
// assuming "<h1>$title</h1>" was found, an id will be
// generated as follows: $id = options.slugFunc($title)
//- the purpose of this function is to generate an id
// value that respects HTML's requirements for these
// kind of values; e.g. no (') or (") characters, etc.
//- node's slug module isn't flawless:
// slug('1.') === slug('1..') === '1'
// i.e. a possible id value collision
//- this option allows you to specify a function of your
// own in case slug() causes any issues
slugFunc: slug,
//- if a heading of the form <h1>$title</h1> is found, an id
// will be generated using '$id = slug($title)'. in order to
// avoid collision of id values, generated ids will be
// prefixed with $idPrefix;
// i.e. '<h1 id="$idPrefix$id">$title</h1>'.
//- set to "" if you don't want to use a prefix.
idPrefix: "doctoc-",
//- this will limit id = (idPrefix + slugFunc(title))
// to the specified number of characters.
//- id values might exceed that limit by some unique
// number suffix.
idLengthLimit: 256,
//- if set to true, this will do check that a generated id is
// not already in use. so a test will be done for each
// id generated!
//- if such a test determines that a generated value is not
// unique, append a counter (=1) to the id's value,
// i.e. '$newId=$id-$counter'. redo the test with the new
// value. if $newId still isn't unique, increment the
// counter and repeat the procedure.
makeIdsUnique: false,
//- set true to always update file.contents;
// even if no new id was generated
alwaysUpdate: false
}
Note that if a hRange value is given, it will override hMin, hMax and hSelector. And if hRange is omitted, but hMin and/or hMax are given, they will override hSelector. So only one of those (hRange, hMin/hMax or hSelector) should be used.
Range/Selector for options
This plugin will accept a range string instead of an options object:
metalsmith-doctoc-options {
...
plugins: {
...
$configName: {
... options: 'h1-6' ...
}
...
},
...
}
It is also possible to provide a selector string:
... options: 'h1, h2, h3, h4' ...
Node.heading objects
These objects will have the following properties:
Heading {
//- e.g. 'h1' in case of '<h1>'
tag: $tag,
//- e.g. '$id' in case of '<h1 id="$id">'
id: $id,
//- e.g. '$title' in case of '<h1>$title</h1>'
title: $title,
//- e.g. 2 in case of '<h2>'
level: $level
}