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 🙏

© 2025 – Pkg Stats / Ryan Hefner

editorsnotes-markup-parser

v6.1.2

Published

Parser for Editors' Notes markup language

Readme

Editors' Notes markup parser

This is parser for a custom flavor of CommonMark that includes extensions for authoring scholarly notes on Editors' Notes. The following additions are supported, based off of conventions in Pandoc and MultiMarkdown.

Features

The Editors' Notes markup language supports the syntax of CommonMark, with several additions

Inline references to Editors' Notes entitites

References to topics and notes can be added within text with the syntax

@@t(TOPIC_ID)

and

@@n(NOTE_ID)

respectively. For example, if topic 140 in a project with the slug p had the name "Woodrow Wilson", the markup

In a contentious election, @@t140 was elected president in 1912.

would result in the html:

  <p>
    In a contentions election, 
    <a href="/projects/p/topics/140/" class="ENInlineReference ENInlineReference-topic">
      Woodrow Wilson
    </a>
    was elected president in 1912.
  </p>

Link references to Editors' Notes entities

Links to topics, documents, and notes can also be added to arbitrary text by including the @@ syntax as link href values. For example, [some text](@@d1) would include a link to the document with ID 1.

Citations

Documents can be cited with the same syntax as used in Pandoc. To cite a document within body text, use the format

`[(optional prefix )@@d(DOCUMENT_ID)(, optional locator)]`

Blockquote attribution

Blockquotes can be attributed to a certain source by using the citation syntax in the final line of the blockquote. For example:

> The whole life of those societies in which modern conditions of production
> prevail presents itself as an immense accumulation of _spectacles_. All that
> once was directly lived has become mere representation.
>
> [@@d40, p.12]

Testing

  • npm install
  • npm test