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

markdown-it-metadata-block

v1.0.2

Published

pandoc compatible metadata blocks for markdown-it

Downloads

13

Readme

markdown-it-metadata-block

Metadata block plugin for markdown-it markdown parser.

Syntax

Syntax based on Pandoc yaml_metadata_block but metadata format is configurable:

A metadata block must either start on the first line or be preceded by a blank line. Metadata blocks are by a line starting with exactly three dashes (---) possibly followed by whitespace. They are closed by three dashes or three dots (...).

The content must parse to a valid object otherwise it will not be interpreted as a metadata block. Metadata blocks are interpreted and merged in sequence.

Options

interface MetadataOptions {
  meta?: object
  parseMetadata: (block: string) => any
}

The parseMetadata option is required. Recommended value: require('yaml').parse. If the function does not return an object or throws an error, the potential metadata block will be interpreted as if the plugins was disabled.

Use

the env object of a parser run will be populated with an object meta which can be used by other plugins. If you want to expose the metadata you have to pass the meta option to the plugin:

import md from 'markdown-it'
import metadata_block from 'markdown-it-metadata-block'
import yaml from 'yaml'

const meta = {} // may be pre-populated with defaults

const markdown = md().use(metadata_block,{
  parseMetadata: yaml.parse,
  meta
})

markdown.render(`
---
a: 1
...

the markdown content

---
b:
- 1
- 2
- 3
...
`)

console.log(meta.a) // 5
console.log(meta.b) // [1,2,3]