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

mocha-markdown

v1.0.0

Published

Transform Markdown lists into JavaScript tests.

Readme

Mocha Markdown

Mocha-Markdown is a tiny utility designed to help reduce the boilerplate involved with writing tests. It lets you transform blocks of Markdown which look like this:

# Requirements
- List the requirements for your application here.
- Each requirement will be transformed into a test for you.
  - If you want to describe more specific properties of a requirement, simply indent the list.
  - Arbitrary levels of indentation should work.
    - Write as much as you like!
- In the end, mocha-markdown will take this list and spit out JavaScript within a file for you.
- By default, the file will be called test.js inside the directory in which you run this tool.

# Application
This text does not matter. mocha-markdown will ignore it.

Into JavaScript code which looks like this:

describe("List the requirements for your application here.", () => {});
describe("Each requirement will be transformed into a test for you.", () => {
  describe("If you want to describe more specific properties of a requirement, simply indent the list.", () => {});
  describe("Arbitrary levels of indentation should work.", () => {
    describe("Write as much as you like!", () => {});
  });
});
describe("In the end, mocha-markdown will take this list and spit out JavaScript within a file for you.", () => {});
describe("By default, the file will be called test.js inside the directory in which you run this tool.", () => {});

That's it! Interesting CLI options are as follows:

  • --inputfile or -i lets you specify which Markdown file you want mocha-markdown to look at. This argument is required.
  • --headers lets you select arbitrary headers within your describe block that contain lists of requirements which you want mocha-markdown to parse.
  • --outputpath or -o lets you specify where you want the file mocha-markdown generates to be.

TODO

  • [X] Finish adding basic functionality.
  • [X] Hook prettier into the code generation.
  • [X] Configure command line interface with yargs.
  • [X] Add more documentation.
  • [ ] Publish project on NPM.
  • [ ] Write a plugin for VSCode.