Gathering detailed insights and metrics for mdast-util-gfm-footnote
Gathering detailed insights and metrics for mdast-util-gfm-footnote
Gathering detailed insights and metrics for mdast-util-gfm-footnote
Gathering detailed insights and metrics for mdast-util-gfm-footnote
mdast-util-gfm-task-list-item
mdast extension to parse and serialize GFM task list items
mdast-util-gfm-strikethrough
mdast extension to parse and serialize GFM strikethrough
mdast-util-gfm
mdast extension to parse and serialize GFM (GitHub Flavored Markdown)
mdast-util-gfm-table
mdast extension to parse and serialize GFM tables
mdast extension to parse and serialize GFM footnotes
npm install mdast-util-gfm-footnote
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
5 Stars
32 Commits
8 Watching
1 Branches
10 Contributors
Updated on 17 Feb 2024
Minified
Minified + Gzipped
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
-0.2%
642,536
Compared to previous day
Last week
5.7%
3,368,679
Compared to previous week
Last month
16.7%
13,796,739
Compared to previous month
Last year
128%
124,214,629
Compared to previous year
mdast extensions to parse and serialize GFM footnotes.
This package contains two extensions that add support for GFM footnote syntax
in markdown to mdast.
These extensions plug into
mdast-util-from-markdown
(to support parsing
footnotes in markdown into a syntax tree) and
mdast-util-to-markdown
(to support serializing
footnotes in syntax trees to markdown).
GFM footnotes were announced September 30, 2021 but are not specified.
Their implementation on github.com is currently buggy.
The bugs have been reported on cmark-gfm
.
You can use these extensions when you are working with
mdast-util-from-markdown
and mdast-util-to-markdown
already.
When working with mdast-util-from-markdown
, you must combine this package
with micromark-extension-gfm-footnote
.
When you don’t need a syntax tree, you can use micromark
directly with micromark-extension-gfm-footnote
.
When you are working with syntax trees and want all of GFM, use
mdast-util-gfm
instead.
All these packages are used remark-gfm
, which
focusses on making it easier to transform content by abstracting these
internals away.
This utility does not handle how markdown is turned to HTML.
That’s done by mdast-util-to-hast
.
If your content is not in English, you should configure that utility.
This package is ESM only. In Node.js (version 16+), install with npm:
1npm install mdast-util-gfm-footnote
In Deno with esm.sh
:
1import {gfmFootnoteFromMarkdown, gfmFootnoteToMarkdown} from 'https://esm.sh/mdast-util-gfm-footnote@2'
In browsers with esm.sh
:
1<script type="module"> 2 import {gfmFootnoteFromMarkdown, gfmFootnoteToMarkdown} from 'https://esm.sh/mdast-util-gfm-footnote@2?bundle' 3</script>
Say our document example.md
contains:
1Hi![^1] 2 3[^1]: big note
…and our module example.js
looks as follows:
1import fs from 'node:fs/promises' 2import {fromMarkdown} from 'mdast-util-from-markdown' 3import {toMarkdown} from 'mdast-util-to-markdown' 4import {gfmFootnote} from 'micromark-extension-gfm-footnote' 5import {gfmFootnoteFromMarkdown, gfmFootnoteToMarkdown} from 'mdast-util-gfm-footnote' 6 7const doc = await fs.readFile('example.md') 8 9const tree = fromMarkdown(doc, { 10 extensions: [gfmFootnote()], 11 mdastExtensions: [gfmFootnoteFromMarkdown()] 12}) 13 14console.log(tree) 15 16const out = toMarkdown(tree, {extensions: [gfmFootnoteToMarkdown()]}) 17 18console.log(out)
…now running node example.js
yields (positional info removed for brevity):
1{ 2 type: 'root', 3 children: [ 4 { 5 type: 'paragraph', 6 children: [ 7 {type: 'text', value: 'Hi!'}, 8 {type: 'footnoteReference', identifier: '1', label: '1'} 9 ] 10 }, 11 { 12 type: 'footnoteDefinition', 13 identifier: '1', 14 label: '1', 15 children: [ 16 {type: 'paragraph', children: [{type: 'text', value: 'big note'}]} 17 ] 18 } 19 ] 20}
1Hi\![^1] 2 3[^1]: big note
This package exports the identifiers
gfmFootnoteFromMarkdown
and
gfmFootnoteToMarkdown
.
There is no default export.
gfmFootnoteFromMarkdown()
Create an extension for
mdast-util-from-markdown
to enable GFM footnotes in markdown.
Extension for mdast-util-from-markdown
(FromMarkdownExtension
).
gfmFootnoteToMarkdown()
Create an extension for
mdast-util-to-markdown
to enable GFM footnotes in markdown.
Extension for mdast-util-to-markdown
(ToMarkdownExtension
).
This utility does not handle how markdown is turned to HTML.
That’s done by mdast-util-to-hast
.
If your content is not in English, you should configure that utility.
See Syntax in micromark-extension-gfm-footnote
.
The following interfaces are added to mdast by this utility.
FootnoteDefinition
1interface FootnoteDefinition <: Parent { 2 type: 'footnoteDefinition' 3 children: [FlowContent] 4} 5 6FootnoteDefinition includes Association
FootnoteDefinition (Parent) represents content relating to the document that is outside its flow.
FootnoteDefinition can be used where flow content is expected. Its content model is also flow content.
FootnoteDefinition includes the mixin Association.
FootnoteDefinition should be associated with FootnoteReferences.
For example, the following markdown:
1[^alpha]: bravo and charlie.
Yields:
1{ 2 type: 'footnoteDefinition', 3 identifier: 'alpha', 4 label: 'alpha', 5 children: [{ 6 type: 'paragraph', 7 children: [{type: 'text', value: 'bravo and charlie.'}] 8 }] 9}
FootnoteReference
1interface FootnoteReference <: Node { 2 type: 'footnoteReference' 3} 4 5FootnoteReference includes Association
FootnoteReference (Node) represents a marker through association.
FootnoteReference can be used where phrasing content is expected. It has no content model.
FootnoteReference includes the mixin Association.
FootnoteReference should be associated with a FootnoteDefinition.
For example, the following markdown:
1[^alpha]
Yields:
1{ 2 type: 'footnoteReference', 3 identifier: 'alpha', 4 label: 'alpha' 5}
FlowContent
(GFM footnotes)1type FlowContentGfm = FootnoteDefinition | FlowContent
PhrasingContent
(GFM footnotes)1type PhrasingContentGfm = FootnoteReference | PhrasingContent
This package is fully typed with TypeScript. It does not export additional types.
The FootnoteDefinition
and FootnoteReference
types of the mdast nodes are
exposed from @types/mdast
.
Projects maintained by the unified collective are compatible with maintained versions of Node.js.
When we cut a new major release, we drop support for unmaintained versions of
Node.
This means we try to keep the current release line,
mdast-util-gfm-footnote@^2
, compatible with Node.js 16.
remark-gfm
— remark plugin to support GFMmdast-util-gfm
— same but all of GFM (autolink literals, footnotes, strikethrough, tables,
tasklists)micromark-extension-gfm-footnote
— micromark extension to parse GFM footnotesSee contributing.md
in syntax-tree/.github
for
ways to get started.
See support.md
for ways to get help.
This project has a code of conduct. By interacting with this repository, organization, or community you agree to abide by its terms.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
security policy file detected
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
no SAST tool detected
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Score
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More