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

editorsnotes-markup-renderer

v2.1.2

Published

Renderer for Editors' Notes markup language

Readme

Editors' Notes markup renderer

A server to render Editors' Notes markup, with support for formatting citations from Zotero or CSL data.

Running

Installing this package will create a binary called editorsnotes_renderer. Run it with editorsnotes_renderer [--host=127.0.0.1] [--port=7194]

API

The server exposes a single root endpoint. It must be POSTed to with a JSON object containing a data key with text that will be parsed as Editors' Notes markup.

One GET parameter is understood by the server, the only_transcluded_items flag. If set, the response will be a JSON object containing document, topic, and note keys containing arrays of the objects which would be transcluded in a rendered note.

If this flag is not set, the response will be an HTML string representing the markup data rendered, with respect to the following POST parameters:

  • url_root (string): The root of all links to items (i.e. /projects/emma/)

  • note (arr): An array of Notes as represented in the Editors' Notes API. Notes' title attributes will be used to generate inline labels.

  • topic (arr): An array of Topics as represented in the Editors' Notes API. Topics' preferred_name attributes will be used to generate inline labels.

  • document (arr): An array of Documents as represented in the Editors' Notes API. Documents' zotero_data, csl_data, and description will be used to generate inline labels or citations, in that order of preference.

  • citation_style (string): CSL style for formatted document citations. Default is chicago-author-date.

The note, topic, and document items will determine the text that will be transcluded into the rendered markup HTML. If a transcluded item has no matching representation, the rendered HTML will include the message ([item type] not found).