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

remark-tableau

v0.1.0

Published

A remark plugin that renders Tableau (ts-tableau) fenced code blocks as HTML tables.

Readme

remark-tableau

A remark plugin that renders ```tableau fenced code blocks (using the ts-tableau library) as HTML tables, for any remark-based Markdown pipeline.

Install

npm install remark-tableau

Usage

remark-tableau replaces each tableau code block with a raw HTML node, and renders the Markdown inside every cell along the way (using a sub-pipeline that automatically inherits any remark-syntax plugins -- GFM, math, footnotes, anything -- already attached to your own pipeline before remarkTableau; attach syntax plugins earlier in the chain if you want them to apply inside table cells too). For the generated HTML to survive into the final output, your pipeline must allow dangerous HTML through remark-rehype and then re-parse it with rehype-raw:

import { unified } from "unified"
import remarkParse from "remark-parse"
import remarkRehype from "remark-rehype"
import rehypeRaw from "rehype-raw"
import rehypeStringify from "rehype-stringify"
import remarkTableau from "remark-tableau"

const file = await unified()
  .use(remarkParse)
  .use(remarkTableau)
  .use(remarkRehype, { allowDangerousHtml: true })
  .use(rehypeRaw)
  .use(rehypeStringify)
  .process(markdown)

console.log(String(file))

Without { allowDangerousHtml: true } on remark-rehype and rehype-raw in the pipeline, the generated tables will be dropped or escaped instead of rendered.

Because rendering cell Markdown is asynchronous, use .process() (as in the example above) or .run() -- not .processSync() / .runSync().

Security

Cell content is rendered as real Markdown, the same as the rest of your document. If you're processing untrusted Markdown, run rehype-sanitize after this plugin in your pipeline -- the same advice that already applies to the rest of a Markdown document applies equally to table cells.

Raw HTML written literally inside cell Markdown source is dropped by default: the cell sub-pipeline doesn't enable allowDangerousHtml, and since plugins queued after remarkTableau (including a consumer's own remark-rehype, { allowDangerousHtml: true } if attached there) aren't replayed into cell rendering, that option can't leak into cells either.