Project: rehypejs/rehype

Package: rehype@12.0.1

  1. Dependents: 0
  2. HTML processor powered by plugins part of the unified collective
  1. unified 181
  2. html 124
  3. rehype 88
  4. tree 44
  5. ast 37
  6. syntax 28
  7. parse 24
  8. stringify 19
  9. serialize 12
  10. abstract 10
  11. process 7


Build Coverage Downloads Size Sponsors Backers Chat

unified processor to add support for parsing from HTML and serializing to HTML.


What is this?

This package is a unified processor with support for parsing HTML as input and serializing HTML as output by using unified with rehype-parse and rehype-stringify.

See the monorepo readme for info on what the rehype ecosystem is.

When should I use this?

You can use this package when you want to use unified, have HTML as input, and want HTML as output. This package is a shortcut for unified().use(rehypeParse).use(rehypeStringify). When the input isn’t HTML (meaning you don’t need rehype-parse) or the output is not HTML (you don’t need rehype-stringify), it’s recommended to use unified directly.

When you’re in a browser, trust your content, don’t need positional info on nodes or formatting options, and value a smaller bundle size, you can use rehype-dom instead.

When you want to inspect and format HTML files in a project on the command line, you can use rehype-cli.


This package is ESM only. In Node.js (version 16+), install with npm:

npm install rehype

In Deno with esm.sh:

import {rehype} from 'https://esm.sh/rehype@13'

In browsers with esm.sh:

<script type="module">
  import {rehype} from 'https://esm.sh/rehype@13?bundle'


Say we have the following module example.js:

import {rehype} from 'rehype'
import rehypeFormat from 'rehype-format'

const file = await rehype().use(rehypeFormat).process(`<!doctype html>
        <html lang=en>



…running that with node example.js yields:

<!doctype html>
<html lang="en">


This package exports the identifier rehype. There is no default export.


Create a new unified processor that already uses rehype-parse and rehype-stringify.

You can add more plugins with use. See unified for more information.


Example: passing options to rehype-parse, rehype-stringify

When you use rehype-parse or rehype-stringify manually you can pass options directly to them with use. Because both plugins are already used in rehype, that’s not possible. To define options for them, you can instead pass options to data:

import {rehype} from 'rehype'
import {reporter} from 'vfile-reporter'

const file = await rehype()
  .data('settings', {
    emitParseErrors: true,
    fragment: true,
    preferUnquoted: true
  .process('<div title="a" title="b"></div>')



1:21-1:21 warning Unexpected duplicate attribute duplicate-attribute hast-util-from-html

⚠ 1 warning
<div title=a></div>


HTML is parsed and serialized according to WHATWG HTML (the living standard), which is also followed by all browsers.

Syntax tree

The syntax tree format used in rehype is hast.


This package is fully typed with TypeScript. It exports no additional types.


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, rehype@^13, compatible with Node.js 16.


As rehype works on HTML, and improper use of HTML can open you up to a cross-site scripting (XSS) attack, use of rehype can also be unsafe. Use rehype-sanitize to make the tree safe.

Use of rehype 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 rehypejs/.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.

Support this effort and give back by sponsoring on OpenCollective!










Boost Note

Markdown Space




MIT © Titus Wormer