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

@jamen/mdc

v0.0.1

Published

Compile directory of markdown into HTML and JSON fragments.

Downloads

9

Readme

mdc

Compile directory of markdown into HTML and JSON fragments.

Install

npm i -g mdc

Usage

mdc *.md -o output/ --no-index? --no-json?

Compiles each markdown file into an HTML file, using an index.json to store the front matters and paths:

$ mdc *.md -o dist
# Results in:
# .
# ├── dist
# │   ├── 2018-06-13-test-article-1.html
# │   ├── 2018-06-13-test-article-2.html
# │   └── index.json
# ├── test-article-1.md
# └── test-article-2.md

With --no-index, instead of an index.json file, separate JSON files of the front matters are created alongside the HTML files (as *-info.json):

$ mdc *.md -o dist --no-index
# Results in:
# .
# ├── dist
# │   ├── 2018-06-13-test-article-1.html
# │   ├── 2018-06-13-test-article-1-info.json
# │   ├── 2018-06-13-test-article-2.html
# │   └── 2018-06-13-test-article-2-info.json
# ├── test-article-1.md
# └── test-article-2.md

With --no-json, JSON and front matter is omitted entirely:

$ mdc *.md -o dist --no-json
# Results in:
# .
# ├── dist
# │   ├── 2018-06-13-test-article-1.html
# │   └── 2018-06-13-test-article-2.html
# ├── test-article-1.md
# └── test-article-2.md

With one input, you can omit -o or --output to use stdout instead:

# Compile to stdout
$ mdc input.md
$ mdc input.md --no-json

Every input must have 'title', 'author', 'created', and 'license' properties.

mdc(input, output?)

Function to compile a markdown file into an HTML file, and returns an info object as a promise. Without output the HTML is returned inside the object.

Features of the compiler:

let result = await mdc('./input.md', './dist')
// result.htmlFile

let result = await mdc('./input.md')
// result.htmlBody

See lib/schema.js for more info on the return value.

License Types

Inspired from markdown-to-medium, the license types are:

  • all-rights-reserved
  • cc-40-by
  • cc-40-by-nd
  • cc-40-by-sa
  • cc-40-by-nc
  • cc-40-by-nc-nd
  • cc-40-by-nc-sa
  • cc-40-zero
  • public-domain