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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@nvanexan/markdoc-extensions

v0.0.2

Published

A tiny library for extending Markdoc parsing

Downloads

5

Readme

markdoc-extensions

A tiny library for extending Markdoc parsing.

Markdoc is amazing, but its parser does not parse some standard markdown tokens that one might wish to parse as Markdoc nodes, rather than as Markdoc tags. These include:

  • Highlights (==some text==)
  • Footnotes ([^1]: footnote)

This parser extends Markdoc's parser by processing these additional items, and exposing some extended nodes that you can add to your Markdoc config.

How to use

  1. Install the package
npm install --save @nvanexan/markdoc-extensions
  1. Create a new instance of the extended parser
const parser = new MarkdocExtendedParser();
  1. Pass in a string or Node object to be parsed
// Passing an existing ast Node already parsed by Markdoc's base parser
const result = parser.parse(ast);

// Passing a string of text
const result = parser.parse("This is a ==test==");

Additional notes

When you initialize the extended parser, you may pass in arguments to have it ignore processing certain extended tokens. For example, if you want to ignore processing footnotes, you can initialize the parser like so:

const parser = new MarkdocExtendedParser({footnotes: false});

By default, both footnotes and highlights will be processed.

Use cases

I am currently using this extended parser and nodes to apply highlights and footnotes in a project that uses Astro and Keystatic for content management. I will update with implementation details on that once the project is complete.