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

markdown-it-popover-notes

v1.0.0

Published

Native HTML popover footnotes for markdown-it markdown parser.

Readme

markdown-it-popover-notes

NPM Version License

Native HTML popover footnotes for markdown-it markdown parser. Based on markdown-it-footnote.

Based on markdown-it-footnote, which you should probably use with custom render methods instead.

Markup is based on pandoc definition.

Usage Examples

Normal Footnotes

Input:

Here is a footnote reference,[^1] and another.[^longnote]

[^1]: Here is the footnote.

[^longnote]: Here’s one with multiple blocks.

    Subsequent paragraphs are indented to show that they belong to the previous footnote.

        { some.code }

    The whole paragraph can be indented, or just the first line. In this way, multi-paragraph footnotes work like multi-paragraph list items.

This paragraph won’t be part of the note, because it isn’t indented.

Output:

<p>Here is a footnote reference,<sup><button popovertarget="ref-1">[1]</button></sup> and another.<sup><button popovertarget="ref-2">[2]</button></sup></p>
<p>This paragraph won’t be part of the note, because it isn’t indented.</p>
<section id="popover-footnotes">
  <aside id="ref-1" popover="auto">
    <p>Here is the footnote.</p>
  </aside>
  <aside id="ref-2" popover="auto">
    <p>Here’s one with multiple blocks.</p>
    <p>Subsequent paragraphs are indented to show that they belong to the previous footnote.</p>
    <pre><code>{ some.code }</code></pre>
    <p>The whole paragraph can be indented, or just the first line. In this way, multi-paragraph footnotes work like multi-paragraph list items.</p>
  </aside>
</section>

Inline Footnotes

Input:

Here is an inline note^[Inlines notes are easier to write.] with some text after.

Output:

<p>Here is an inline note<sup><button popovertarget="ref-1">[1]</button></sup> with some text after.</p>
<section id="popover-footnotes">
  <aside id="ref-1" popover="auto">
    <p>Inlines notes are easier to write.</p>
  </aside>
</section>

Installation

Install markdown-it-popover-notes from npm with your favorite package manager.

Usage

import MarkdownIt from "markdown-it";
import popoverNotesPlugin from "markdown-it-popover-notes";

const md = MarkdownIt();
md.use(popoverNotesPlugin);

const html = md.render("Footnotes are cool, but popovers are cooler.^[Popovers are cooler because they don't make the page move!]");

Styling

Without a little CSS, the popovers float in the middle of the screen instead of appearing next to the superscript reference. Below are some minimal styles to get you started. There is a more detailed example in styling-sample.html.

button[popovertarget] {
  background: unset;
  border: unset;
  color: LinkText;
  cursor: pointer;
}

[popover] {
  position-area: block-start;
  position-try-fallbacks: flip-block flip-inline;
  margin: 0.5rem;
  padding: 0.5rem;
  inset: auto;
}