Gathering detailed insights and metrics for mdast-util-from-markdown
Gathering detailed insights and metrics for mdast-util-from-markdown
Gathering detailed insights and metrics for mdast-util-from-markdown
Gathering detailed insights and metrics for mdast-util-from-markdown
mdast-util-gfm
mdast extension to parse and serialize GFM (GitHub Flavored Markdown)
mdast-util-gfm-strikethrough
mdast extension to parse and serialize GFM strikethrough
mdast-util-gfm-task-list-item
mdast extension to parse and serialize GFM task list items
mdast-util-to-string
mdast utility to get the plain text content of a node
npm install mdast-util-from-markdown
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
213 Stars
158 Commits
20 Forks
10 Watching
1 Branches
12 Contributors
Updated on 23 Nov 2024
Minified
Minified + Gzipped
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
-1.7%
1,806,734
Compared to previous day
Last week
3.8%
9,540,416
Compared to previous week
Last month
15%
39,487,944
Compared to previous month
Last year
61%
391,745,580
Compared to previous year
12
mdast utility that turns markdown into a syntax tree.
This package is a utility that takes markdown input and turns it into an mdast syntax tree.
This utility uses micromark
, which turns markdown into tokens,
and then turns those tokens into nodes.
This package is used inside remark-parse
, which focusses on
making it easier to transform content by abstracting these internals away.
If you want to handle syntax trees manually, use this.
When you just want to turn markdown into HTML, use micromark
instead.
For an easier time processing content, use the remark ecosystem instead.
You can combine this package with other packages to add syntax extensions to
markdown.
Notable examples that deeply integrate with this package are
mdast-util-gfm
,
mdast-util-mdx
,
mdast-util-frontmatter
,
mdast-util-math
, and
mdast-util-directive
.
This package is ESM only. In Node.js (version 16+), install with npm:
1npm install mdast-util-from-markdown
In Deno with esm.sh
:
1import {fromMarkdown} from 'https://esm.sh/mdast-util-from-markdown@2'
In browsers with esm.sh
:
1<script type="module"> 2 import {fromMarkdown} from 'https://esm.sh/mdast-util-from-markdown@2?bundle' 3</script>
Say we have the following markdown file example.md
:
1## Hello, *World*!
…and our module example.js
looks as follows:
1import fs from 'node:fs/promises' 2import {fromMarkdown} from 'mdast-util-from-markdown' 3 4const doc = await fs.readFile('example.md') 5const tree = fromMarkdown(doc) 6 7console.log(tree)
…now running node example.js
yields (positional info removed for brevity):
1{ 2 type: 'root', 3 children: [ 4 { 5 type: 'heading', 6 depth: 2, 7 children: [ 8 {type: 'text', value: 'Hello, '}, 9 {type: 'emphasis', children: [{type: 'text', value: 'World'}]}, 10 {type: 'text', value: '!'} 11 ] 12 } 13 ] 14}
This package exports the identifier fromMarkdown
.
There is no default export.
The export map supports the development
condition.
Run node --conditions development example.js
to get instrumented dev code.
Without this condition, production code is loaded.
fromMarkdown(value[, encoding][, options])
Turn markdown into a syntax tree.
(value: Value, encoding: Encoding, options?: Options) => Root
(value: Value, options?: Options) => Root
value
(Value
)
— markdown to parseencoding
(Encoding
, default: 'utf8'
)
— character encoding for when value
is
Uint8Array
options
(Options
, optional)
— configurationmdast tree (Root
).
CompileContext
mdast compiler context (TypeScript type).
stack
(Array<Node>
)
— stack of nodestokenStack
(Array<[Token, OnEnterError | undefined]>
)
— stack of tokensdata
(CompileData
)
— info passed around; key/value storebuffer
(() => undefined
)
— capture some of the output dataresume
(() => string
)
— stop capturing and access the output dataenter
((node: Node, token: Token, onError?: OnEnterError) => undefined
)
— enter a nodeexit
((token: Token, onError?: OnExitError) => undefined
)
— exit a nodesliceSerialize
((token: Token, expandTabs?: boolean) => string
)
— get the string value of a tokenconfig
(Required<Extension>
)
— configurationCompileData
Interface of tracked data (TypeScript type).
1interface CompileData { /* see code */ }
When working on extensions that use more data, extend the corresponding interface to register their types:
1declare module 'mdast-util-from-markdown' { 2 interface CompileData { 3 // Register a new field. 4 mathFlowInside?: boolean | undefined 5 } 6}
Encoding
Encodings supported by the Uint8Array
class (TypeScript type).
See micromark
for more info.
1type Encoding = 'utf8' | /* … */
Extension
Change how markdown tokens from micromark are turned into mdast (TypeScript type).
canContainEols
(Array<string>
, optional)
— token types where line endings are usedenter
(Record<string, Handle>
, optional)
— opening handlesexit
(Record<string, Handle>
, optional)
— closing handlestransforms
(Array<Transform>
, optional)
— tree transformsHandle
Handle a token (TypeScript type).
this
(CompileContext
)
— contexttoken
(Token
)
— current tokenNothing (undefined
).
OnEnterError
Handle the case where the right
token is open, but it is closed (by the
left
token) or because we reached the end of the document (TypeScript type).
this
(CompileContext
)
— contextleft
(Token
or undefined
)
— left tokenright
(Token
)
— right tokenNothing (undefined
).
OnExitError
Handle the case where the right
token is open but it is closed by
exiting the left
token (TypeScript type).
this
(CompileContext
)
— contextleft
(Token
)
— left tokenright
(Token
)
— right tokenNothing (undefined
).
Options
Configuration (TypeScript type).
extensions
(Array<MicromarkExtension>
, optional)
— micromark extensions to change how markdown is parsedmdastExtensions
(Array<Extension | Array<Extension>>
,
optional)
— extensions for this utility to change how tokens are turned into a treeToken
Token from micromark (TypeScript type).
1type Token = { /* … */ }
Transform
Extra transform, to change the AST afterwards (TypeScript type).
tree
(Root
)
— tree to transformNew tree (Root
) or nothing (in which case the current tree is used).
Value
Contents of the file (TypeScript type).
See micromark
for more info.
1type Value = Uint8Array | string
syntax-tree/mdast-util-directive
— directivessyntax-tree/mdast-util-frontmatter
— frontmatter (YAML, TOML, more)syntax-tree/mdast-util-gfm
— GFMsyntax-tree/mdast-util-gfm-autolink-literal
— GFM autolink literalssyntax-tree/mdast-util-gfm-footnote
— GFM footnotessyntax-tree/mdast-util-gfm-strikethrough
— GFM strikethroughsyntax-tree/mdast-util-gfm-table
— GFM tablessyntax-tree/mdast-util-gfm-task-list-item
— GFM task list itemssyntax-tree/mdast-util-math
— mathsyntax-tree/mdast-util-mdx
— MDXsyntax-tree/mdast-util-mdx-expression
— MDX expressionssyntax-tree/mdast-util-mdx-jsx
— MDX JSXsyntax-tree/mdast-util-mdxjs-esm
— MDX ESMMarkdown is parsed according to CommonMark. Extensions can add support for other syntax. If you’re interested in extending markdown, more information is available in micromark’s readme.
The syntax tree is mdast.
This package is fully typed with TypeScript.
It exports the additional types CompileContext
,
CompileData
,
Encoding
,
Extension
,
Handle
,
OnEnterError
,
OnExitError
,
Options
,
Token
,
Transform
, and
Value
.
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-from-markdown@^2
, compatible with Node.js 16.
As markdown is sometimes used for HTML, and improper use of HTML can open you up
to a cross-site scripting (XSS) attack, use of mdast-util-from-markdown
can also be unsafe.
When going to HTML, use this utility in combination with
hast-util-sanitize
to make the tree safe.
syntax-tree/mdast-util-to-markdown
— serialize mdast as markdownmicromark/micromark
— parse markdownremarkjs/remark
— process markdownSee 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 dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
0 existing vulnerabilities detected
Reason
security policy file detected
Details
Reason
9 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 9
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
no SAST tool detected
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
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