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-yadda

v0.2.3

Published

Integrate yadda features and steps with mocha tests.

Readme

mocha-yadda

npm version

Module to integrate yadda with mocha for both browser and node.js tests. The yadda project includes in its docs and examples a little bit of glue code to accomplish this integration. This package tries to build on and improve that, offering some conveniences for testing in different environments like loading Gherkin files from a Karma instance or the local file system when running directly with Mocha.

To use, create a test source that Mocha will find and execute of the form:

var fdescribe = require('mocha-yadda').fdescribe;

fdescribe('path/to/featurefile.feature', [array, of, step, libraries]);

fdescribe also accepts an options object.

  • timeout: override the default timeout for tests set by Mocha on a per feature basis.
  • ctx: feature wide context, for instance to share some stubs or other necessary info or resources
  • beforeFeature/afterFeature: hooks that will run before/after the feature, will bind to the ctx object in provided
  • beforeScenario/afterScenario: hooks that will run before/after each scenario, will bind to the ctx object in provided
  • tags: an array of strings, only a feature or scenario that has a matching tag annotation will be run (as of 0.2.0)

fdescribe supports .only and .skip, like mocha, though .only doesn't interact with any plain Mocha tests. .only will limit execution among a group of mocha-yadda features so it best used with mocha's ability to limit test by files or regexes to limit to just yadda based tests.

For now, mocha-yadda intentionally only supports describing a single feature at a time rather than using yadda's search capabilities. fdescribe can be called multiple times in your bootstrap test to group some or all of your features together.