Gathering detailed insights and metrics for mdast-util-gfm-autolink-literal
Gathering detailed insights and metrics for mdast-util-gfm-autolink-literal
Gathering detailed insights and metrics for mdast-util-gfm-autolink-literal
Gathering detailed insights and metrics for mdast-util-gfm-autolink-literal
mdast extension to parse and serialize GFM autolink literals
npm install mdast-util-gfm-autolink-literal
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
12 Stars
74 Commits
6 Forks
9 Watching
1 Branches
12 Contributors
Updated on 20 Oct 2024
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
-0.9%
778,862
Compared to previous day
Last week
5.7%
4,118,290
Compared to previous week
Last month
16.7%
16,831,672
Compared to previous month
Last year
95.7%
159,133,248
Compared to previous year
mdast extensions to parse and serialize GFM autolink literals.
This package contains two extensions that add support for GFM autolink literals
syntax in markdown to mdast.
These extensions plug into
mdast-util-from-markdown
(to support parsing
GFM autolinks in markdown into a syntax tree) and
mdast-util-to-markdown
(to support serializing
GFM autolinks in syntax trees to markdown).
GitHub employs different algorithms to autolink: one at parse time and one at
transform time (similar to how @mentions
are done at transform time).
This difference can be observed because character references and escapes are
handled differently.
But also because issues/PRs/comments omit (perhaps by accident?) the second
algorithm for www.
, http://
, and https://
links (but not for email links).
As the corresponding micromark extension
micromark-extension-gfm-autolink-literal
is a syntax extension,
it can only perform the first algorithm.
The tree extension gfmAutolinkLiteralFromMarkdown
from this package can
perform the second algorithm, and as they are combined, both are done.
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-autolink-literal
.
When you don’t need a syntax tree, you can use micromark
directly with micromark-extension-gfm-autolink-literal
.
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
.
This package is ESM only. In Node.js (version 16+), install with npm:
1npm install mdast-util-gfm-autolink-literal
In Deno with esm.sh
:
1import {gfmAutolinkLiteralFromMarkdown, gfmAutolinkLiteralToMarkdown} from 'https://esm.sh/mdast-util-gfm-autolink-literal@2'
In browsers with esm.sh
:
1<script type="module"> 2 import {gfmAutolinkLiteralFromMarkdown, gfmAutolinkLiteralToMarkdown} from 'https://esm.sh/mdast-util-gfm-autolink-literal@2?bundle' 3</script>
Say our document example.md
contains:
1www.example.com, https://example.com, and contact@example.com.
…and our module example.js
looks as follows:
1import fs from 'node:fs/promises' 2import {gfmAutolinkLiteral} from 'micromark-extension-gfm-autolink-literal' 3import {fromMarkdown} from 'mdast-util-from-markdown' 4import { 5 gfmAutolinkLiteralFromMarkdown, 6 gfmAutolinkLiteralToMarkdown 7} from 'mdast-util-gfm-autolink-literal' 8import {toMarkdown} from 'mdast-util-to-markdown' 9 10const doc = await fs.readFile('example.md') 11 12const tree = fromMarkdown(doc, { 13 extensions: [gfmAutolinkLiteral()], 14 mdastExtensions: [gfmAutolinkLiteralFromMarkdown()] 15}) 16 17console.log(tree) 18 19const out = toMarkdown(tree, {extensions: [gfmAutolinkLiteralToMarkdown()]}) 20 21console.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 { 8 type: 'link', 9 title: null, 10 url: 'http://www.example.com', 11 children: [{type: 'text', value: 'www.example.com'}] 12 }, 13 {type: 'text', value: ', '}, 14 { 15 type: 'link', 16 title: null, 17 url: 'https://example.com', 18 children: [{type: 'text', value: 'https://example.com'}] 19 }, 20 {type: 'text', value: ', and '}, 21 { 22 type: 'link', 23 title: null, 24 url: 'mailto:contact@example.com', 25 children: [{type: 'text', value: 'contact@example.com'}] 26 }, 27 {type: 'text', value: '.'} 28 ] 29 } 30 ] 31}
1[www.example.com](http://www.example.com), <https://example.com>, and <contact@example.com>.
This package exports the identifiers
gfmAutolinkLiteralFromMarkdown
and
gfmAutolinkLiteralToMarkdown
.
There is no default export.
gfmAutolinkLiteralFromMarkdown()
Create an extension for mdast-util-from-markdown
to enable GFM autolink literals in markdown.
Extension for mdast-util-to-markdown
to enable GFM autolink literals
(FromMarkdownExtension
).
gfmAutolinkLiteralToMarkdown()
Create an extension for mdast-util-to-markdown
to
enable GFM autolink literals in markdown.
Extension for mdast-util-to-markdown
to enable GFM autolink literals
(ToMarkdownExtension
).
This utility does not handle how markdown is turned to HTML.
That’s done by mdast-util-to-hast
.
See Syntax in micromark-extension-gfm-autolink-literal
.
There are no interfaces added to mdast by this utility, as it reuses the existing Link interface.
This package is fully typed with TypeScript. It does not export additional types.
The Link
type of the mdast nodes is 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-autolink-literal@^2
, compatible with Node.js 16.
This utility works with mdast-util-from-markdown
version 2+ and
mdast-util-to-markdown
version 2+.
remarkjs/remark-gfm
— remark plugin to support GFMsyntax-tree/mdast-util-gfm
— same but all of GFM (autolink literals, footnotes, strikethrough, tables,
tasklists)micromark/micromark-extension-gfm-autolink-literal
— micromark extension to parse GFM autolink literalsSee 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.
MIT © Titus Wormer
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
security policy file detected
Details
Reason
0 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 1
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no SAST tool detected
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 Moremdast-util-gfm
mdast extension to parse and serialize GFM (GitHub Flavored Markdown)
micromark-extension-gfm-autolink-literal
micromark extension to support GFM autolink literals
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