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

@ezakto/mocha-md

v0.1.0

Published

Write Mocha tests in Markdown

Downloads

5

Readme

mocha-md

Write mocha tests in markdown

Install

$ npm install -g mocha-md

Usage

Put you markdown test files under test/. Run $ mocha-md.

Test files will be transpiled to js, placed under .test/ and mocha will be run against them.

Tests syntax

Initialization

Add any initialization code in a code block before any test.

describe()

Headings are used to describe() a set of tests. Deeper level headings will result in nesting:

# Arrays

## #indexOf()

Will result in

describe("Arrays", function() {
  describe("#indexOf()", function() {});
});

it()

Paragraphs followed by a code block will translate to individual tests:

should return -1 when value is not present

```js
assert.equal(-1, [1,2,3].indexOf(4));
```

Will result in:

it("should return -1 when value is not present", function() {
  assert.equal(-1, [1, 2, 3].indexOf(4));
});

You can set before, after, beforeEach, afterEach, only and skip like this:

(before) initialize some extra stuff

```js
var ok = true;
```

Resulting in:

before("initialize some extra stuff", function() {
  var ok = true;
});

Async tests

You can set (async) to add a done callback argument to the test:

(async) should return -1 when value is not present

```js
setTimeout(() => {
  assert.equal(-1, [1,2,3].indexOf(4));
  assert.equal(-1, [1,2,3].indexOf(4));
  done()
}, 10);
```

Resulting in:

it("should return -1 when value is not present", function(done) {
  setTimeout(() => {
    assert.equal(-1, [1, 2, 3].indexOf(4));
    assert.equal(-1, [1, 2, 3].indexOf(4));
    done();
  }, 10);
});

You can combine (async) with other flags like this:

(beforeEach) (async) initialize test

```js
"before every test";
done();
```

Result:

beforeEach(function(done) {
  "before every test";
  done();
});