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

comark-footnotes

v0.11.0

Published

Footnotes in Comark: [^1] references, [^1]: definitions over several lines and blocks, and ^[inline notes], in place of comark/plugins/footnotes.

Readme

comark-footnotes

npm version npm downloads license docs

Footnotes in Comark, in place of comark/plugins/footnotes: [^1] references, [^1]: definitions that hold any Markdown over several lines and blocks, and ^[inline notes]. A parse plugin with no components, so it works in any renderer.

pnpm add comark comark-footnotes
import { parseMarkdown } from "comark";
import footnotes from "comark-footnotes";

const document = await parseMarkdown(markdown, {
  plugins: [footnotes()],
});
The deploy waits when the roof holds more than 12 pigeons[^count], unless it's a hotfix^[Two approvals.].

[^count]: Counted once, from the window,
    at 9:00.

    Pigeons that fly off mid-count still count.

Notes are numbered in the order they're first referenced and listed in a section at the end. It takes the same options as Comark's plugin (label, hr, backRef) and writes the same nodes. Remove comark/plugins/footnotes when you add this one.

Compared with Comark's plugin, a definition inside fenced code stays in the code, Markdown in a note renders, and a note can run over several lines and blocks. A reference used twice gets its own id, fnref-label-2.

Issues

A reference with no definition stays as text, and a definition nothing references is dropped. Each adds a sentence to meta.issues:

footnotes: [^gone] has no definition; add a "[^gone]: …" line, or remove the reference.
footnotes: [^spare]: is never referenced; add [^spare] where it applies, or remove the definition.

Credits

The parser is ported from markdown-it-footnote by Vitaly Puzrin and Alex Kocharin, MIT.