Project: remarkjs/remark

Package: remark-stringify@10.0.2

  1. Dependents: 0
  2. remark plugin to add support for serializing markdown
  1. remark 193
  2. unified 178
  3. markdown 140
  4. plugin 138
  5. mdast 87
  6. remark-plugin 76
  7. tree 44
  8. ast 37
  9. syntax 27
  10. stringify 19
  11. compile 14
  12. serialize 12
  13. abstract 10


Build Coverage Downloads Size Sponsors Backers Chat

remark plugin to add support for serializing markdown.


What is this?

This package is a unified (remark) plugin that defines how to take a syntax tree as input and turn it into serialized markdown.

This plugin is built on mdast-util-to-markdown, which turns mdast syntax trees into a string. remark focusses on making it easier to transform content by abstracting such internals away.

unified is a project that transforms content with abstract syntax trees (ASTs). remark adds support for markdown to unified. mdast is the markdown AST that remark uses. This is a remark plugin that defines how mdast is turned into markdown.

When should I use this?

This plugin adds support to unified for serializing markdown. You can alternatively use remark instead, which combines unified, remark-parse, and this plugin.

You can combine this plugin with other plugins to add syntax extensions. Notable examples that deeply integrate with it are remark-gfm, remark-mdx, remark-frontmatter, remark-math, and remark-directive. You can also use any other remark plugin before remark-stringify.

If you want to handle syntax trees manually, you can use mdast-util-to-markdown.


This package is ESM only. In Node.js (version 12.20+, 14.14+, or 16.0+), install with npm:

npm install remark-stringify

In Deno with esm.sh:

import remarkStringify from 'https://esm.sh/remark-stringify@10'

In browsers with esm.sh:

<script type="module">
  import remarkStringify from 'https://esm.sh/remark-stringify@10?bundle'


Say we have the following module example.js:

import {unified} from 'unified'
import rehypeParse from 'rehype-parse'
import rehypeRemark from 'rehype-remark'
import remarkStringify from 'remark-stringify'


async function main() {
  const file = await unified()
    .use(remarkStringify, {
      bullet: '*',
      fence: '~',
      fences: true,
      incrementListMarker: false
    .process('<h1>Hello, world!</h1>')


Running that with node example.js yields:

# Hello, world!


This package exports no identifiers. The default export is remarkStringify.

unified().use(remarkStringify[, options])

Add support for serializing markdown. Options are passed to mdast-util-to-markdown: all formatting options are supported.


Configuration (optional).


Marker to use for bullets of items in unordered lists ('*', '+', or '-', default: '*').


Marker to use in certain cases where the primary bullet doesn’t work ('*', '+', or '-', default: depends). See mdast-util-to-markdown for more information.


Marker to use for bullets of items in ordered lists ('.' or ')', default: '.').


Marker to use in certain cases where the primary bullet for ordered items doesn’t work ('.' or ')', default: none). See mdast-util-to-markdown for more information.


Whether to add the same number of number signs (#) at the end of an ATX heading as the opening sequence (boolean, default: false).


Marker to use for emphasis ('*' or '_', default: '*').


Marker to use for fenced code ('`' or '~', default: '`').


Whether to use fenced code always (boolean, default: false). The default is to use fenced code if there is a language defined, if the code is empty, or if it starts or ends in blank lines.


Whether to increment the counter of ordered lists items (boolean, default: true).


How to indent the content of list items ('one', 'tab', or 'mixed', default: 'tab'). Either with the size of the bullet plus one space (when 'one'), a tab stop ('tab'), or depending on the item and its parent list ('mixed', uses 'one' if the item and list are tight and 'tab' otherwise).


Marker to use for titles ('"' or "'", default: '"').

Whether to always use resource links (boolean, default: false). The default is to use autolinks (<https://example.com>) when possible and resource links ([text](url)) otherwise.


Marker to use for thematic breaks ('*', '-', or '_', default: '*').


Number of markers to use for thematic breaks (number, default: 3, min: 3).


Whether to add spaces between markers in thematic breaks (boolean, default: false).


Whether to use setext headings when possible (boolean, default: false). The default is to always use ATX headings (# heading) instead of setext headings (heading\n=======). Setext headings can’t be used for empty headings or headings with a rank of three or more.


Marker to use for strong ('*' or '_', default: '*').


Whether to join definitions without a blank line (boolean, default: false). The default is to add blank lines between any flow (“block”) construct.


This option is a bit advanced as it requires knowledge of ASTs, so we defer to the documentation available in mdast-util-to-markdown.


This option is a bit advanced as it requires knowledge of ASTs, so we defer to the documentation available in mdast-util-to-markdown.


This option is a bit advanced as it requires deep knowledge of markdown, so we defer to the documentation available in mdast-util-to-markdown.


Markdown is serialized according to CommonMark but care is taken to format in such a way that the resulting markdown should work with most markdown parsers. Other plugins can add support for syntax extensions.

Syntax tree

The syntax tree format used in remark is mdast.


This package is fully typed with TypeScript. An Options type is exported, which models the interface of accepted options.


As markdown can be turned into HTML and improper use of HTML can open you up to cross-site scripting (XSS) attacks, use of remark can be unsafe. When going to HTML, you will likely combine remark with rehype, in which case you should use rehype-sanitize.

Use of remark plugins could also open you up to other attacks. Carefully assess each plugin and the risks involved in using them.

For info on how to submit a report, see our security policy.


See contributing.md in remarkjs/.github for ways to get started. See support.md for ways to get help. Join us in Discussions to chat with the community and contributors.

This project has a code of conduct. By interacting with this repository, organization, or community you agree to abide by its terms.

Support this effort and give back by sponsoring on OpenCollective!










Boost Note




MIT © Titus Wormer