599a376 switched from markdown-it-anchor to markdown-it-named-headers, but the latter seems to be inconsistent with GitHub style links (qv toc_filter.rb), and hence with the remark remark-autolink-headings plugin, etc. Also markdown-it-named-headers has lower npm download figures than markdown-it-anchor.
The handling of punctuation seems to be different from GitHub, and also with markdown-it-named-headers, anchors in headings get included in the id. It is also arguably broken in its own right (e.g. italic formatting in a header can result in leading/trailing hyphens).
The incompatibility with GitHub styling in particular makes the idInHeadings option almost useless to me.
Could you go back to markdown-it-anchor?
599a376 switched from
markdown-it-anchortomarkdown-it-named-headers, but the latter seems to be inconsistent with GitHub style links (qv toc_filter.rb), and hence with the remarkremark-autolink-headingsplugin, etc. Alsomarkdown-it-named-headershas lower npm download figures thanmarkdown-it-anchor.The handling of punctuation seems to be different from GitHub, and also with
markdown-it-named-headers, anchors in headings get included in the id. It is also arguably broken in its own right (e.g. italic formatting in a header can result in leading/trailing hyphens).The incompatibility with GitHub styling in particular makes the
idInHeadingsoption almost useless to me.Could you go back to
markdown-it-anchor?