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

@knight-owl-llc/pandoc-parser

v0.4.0

Published

Pandoc's markdown reader, ported: Pandoc's AST with source positions

Readme

@knight-owl-llc/pandoc-parser

Pandoc 3.11's Markdown reader, ported to JavaScript: a document's AST as Pandoc reads it, each node with the span of source it was read from.

The AST is Pandoc's JSON with a start and end on each node: JSON.stringify(withoutSpans(doc)) equals pandoc -f markdown -t json on the same text. The reader runs with Pandoc's default Markdown extensions and reads raw TeX with a port of Pandoc's LaTeX reader.

Use

import { readMarkdown } from "@knight-owl-llc/pandoc-parser";

const doc = readMarkdown(text, { tabStop: 4 });
doc.blocks[0].start; // where the first block starts in `text`

| Export | What it is | | ----------------------------------- | --------------------------------------------------------------------------------- | | readMarkdown(text, {tabStop}) | The document as Pandoc's Markdown reader reads it | | readLaTeX(text, options) | The document as Pandoc's LaTeX reader reads it | | withoutSpans(value) | A read without its spans: Pandoc's JSON | | toSources(files) | Files joined as Pandoc's CLI joins them, with a lookup from an offset to its file | | continuesParagraph(next, options) | Whether Pandoc reads a paragraph on into the line next | | DEFAULT_TAB_STOP | Pandoc's default --tab-stop, 4 |

A Markdown read also carries four properties outside its JSON:

| Property | What it holds | | ---------------- | ----------------------------------------------------------------------------------- | | definitions | Each reference definition, with the span of each of its parts | | log | The messages Pandoc logs reading it, in order, each with Pandoc's fields and a span | | unresolved | Each reference and note looked up and not found: kind, form, label and span | | metadataBlocks | Each YAML metadata block and title block read for metadata, with its span |

Offsets are UTF-16 code units, as JavaScript indexes a string.

License

GPL-2.0-or-later, as Pandoc's: LICENSE. NOTICE.md gives the port's provenance and the notices of the libraries ported with it.