Gathering detailed insights and metrics for mdast-util-gfm-strikethrough
Gathering detailed insights and metrics for mdast-util-gfm-strikethrough
Gathering detailed insights and metrics for mdast-util-gfm-strikethrough
Gathering detailed insights and metrics for mdast-util-gfm-strikethrough
mdast extension to parse and serialize GFM strikethrough
npm install mdast-util-gfm-strikethrough
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
5 Stars
60 Commits
4 Forks
9 Watching
1 Branches
11 Contributors
Updated on 17 Feb 2024
Minified
Minified + Gzipped
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
-5.8%
712,294
Compared to previous day
Last week
4%
4,100,472
Compared to previous week
Last month
11.3%
16,852,684
Compared to previous month
Last year
95.9%
160,293,849
Compared to previous year
mdast extensions to parse and serialize GFM strikethrough.
This package contains two extensions that add support for GFM strikethrough
syntax in markdown to mdast.
These extensions plug into
mdast-util-from-markdown
(to support parsing
strikethrough in markdown into a syntax tree) and
mdast-util-to-markdown
(to support serializing
strikethrough in syntax trees to markdown).
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-strikethrough
.
When you don’t need a syntax tree, you can use micromark
directly with micromark-extension-gfm-strikethrough
.
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 you want a different element, you should configure that utility.
This package is ESM only. In Node.js (version 16+), install with npm:
1npm install mdast-util-gfm-strikethrough
In Deno with esm.sh
:
1import {gfmStrikethroughFromMarkdown, gfmStrikethroughToMarkdown} from 'https://esm.sh/mdast-util-gfm-strikethrough@2'
In browsers with esm.sh
:
1<script type="module"> 2 import {gfmStrikethroughFromMarkdown, gfmStrikethroughToMarkdown} from 'https://esm.sh/mdast-util-gfm-strikethrough@2?bundle' 3</script>
Say our document example.md
contains:
1*Emphasis*, **importance**, and ~~strikethrough~~.
…and our module example.js
looks as follows:
1import fs from 'node:fs/promises' 2import {gfmStrikethrough} from 'micromark-extension-gfm-strikethrough' 3import {fromMarkdown} from 'mdast-util-from-markdown' 4import {gfmStrikethroughFromMarkdown, gfmStrikethroughToMarkdown} from 'mdast-util-gfm-strikethrough' 5import {toMarkdown} from 'mdast-util-to-markdown' 6 7const doc = await fs.readFile('example.md') 8 9const tree = fromMarkdown(doc, { 10 extensions: [gfmStrikethrough()], 11 mdastExtensions: [gfmStrikethroughFromMarkdown()] 12}) 13 14console.log(tree) 15 16const out = toMarkdown(tree, {extensions: [gfmStrikethroughToMarkdown()]}) 17 18console.log(out)
Now, running node example
yields:
1{ 2 type: 'root', 3 children: [ 4 { 5 type: 'paragraph', 6 children: [ 7 {type: 'emphasis', children: [{type: 'text', value: 'Emphasis'}]}, 8 {type: 'text', value: ', '}, 9 {type: 'strong', children: [{type: 'text', value: 'importance'}]}, 10 {type: 'text', value: ', and '}, 11 {type: 'delete', children: [{type: 'text', value: 'strikethrough'}]}, 12 {type: 'text', value: '.'} 13 ] 14 } 15 ] 16}
1*Emphasis*, **importance**, and ~~strikethrough~~.
This package exports the identifiers
gfmStrikethroughFromMarkdown
and
gfmStrikethroughToMarkdown
.
There is no default export.
gfmStrikethroughFromMarkdown()
Create an extension for mdast-util-from-markdown
to enable GFM strikethrough in markdown.
Extension for mdast-util-from-markdown
to enable GFM strikethrough
(FromMarkdownExtension
).
gfmStrikethroughToMarkdown()
Create an extension for mdast-util-to-markdown
to
enable GFM strikethrough in markdown.
Extension for mdast-util-to-markdown
to enable GFM strikethrough
(ToMarkdownExtension
).
This utility does not handle how markdown is turned to HTML.
That’s done by mdast-util-to-hast
.
If you want a different element, you should configure that utility.
See Syntax in micromark-extension-gfm-strikethrough
.
The following interfaces are added to mdast by this utility.
Delete
1interface Delete <: Parent { 2 type: 'delete' 3 children: [TransparentContent] 4}
Delete (Parent) represents contents that are no longer accurate or no longer relevant.
Delete can be used where phrasing content is expected. Its content model is transparent content.
For example, the following markdown:
1~~alpha~~
Yields:
1{ 2 type: 'delete', 3 children: [{type: 'text', value: 'alpha'}] 4}
PhrasingContent
(GFM strikethrough)1type PhrasingContentGfm = Delete | PhrasingContent
This package is fully typed with TypeScript. It does not export additional types.
The Delete
type of the mdast node 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-strikethrough@^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-strikethrough
— micromark extension to parse GFM strikethroughSee 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
license file detected
Details
Reason
0 existing vulnerabilities detected
Reason
security policy file detected
Details
Reason
Found 1/30 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
Reason
SAST tool is not run on all commits -- score normalized to 0
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