npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@twinkleplop/rehype

v0.1.5

Published

Highlight fenced code and inline code in a [rehype](https://github.com/rehypejs/rehype) pipeline.

Readme

@twinkleplop/rehype

Highlight fenced code and inline code in a rehype pipeline.

import rehype_stringify from "rehype-stringify";
import remark_parse from "remark-parse";
import remark_rehype from "remark-rehype";
import { unified } from "unified";
import rehype_twinkleplop from "@twinkleplop/rehype";
import { language as typescript } from "@twinkleplop/typescript";

const pipeline = unified()
  .use(remark_parse)
  .use(remark_rehype)
  .use(rehype_twinkleplop, {
    languages: { ts: typescript(), js: "ts" },
  })
  .use(rehype_stringify);

The plugin replaces each pre > code element with highlighted HTML parsed into hast nodes.

output

Parsing the HTML adds processing time. Set output: "raw" to return the highlighted string as a raw node:

.use(rehype_twinkleplop, { languages, output: "raw" });

"raw" needs allowDangerousHtml on rehype-stringify (or rehype-raw before it), otherwise the stringifier escapes the block and displays the HTML as text.

Both modes render the same code. In the default mode, the pipeline's stringifier may use different HTML entities, such as < for <. Raw mode preserves Twinkleplop's HTML string, as the markdown-it and remark plugins do.

The language comes from the code element's language-<name> class and the meta string from data.meta, which remark-rehype sets, or from a metastring attribute for a tree that came from HTML.

Errors name the file and line whenever the tree carries positions.

See @twinkleplop/markdown-core for shared options, fence metadata and HTML output.