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

generator-mocha-testem

v0.1.4

Published

Yeoman generator for Mocha+Testem

Readme

Mocha+Testem generator Build Status

Getting Started

Install:

npm install -g generator-mocha-testem

Usage

yo mocha-testem
testem

How to use with generator-webapp

This assumes you're starting a new project.

  • mkdir myproject && cd myproject
  • yo webapp
  • Delete the test directory: rm -rf test
  • yo mocha-testem
  • Run testem. It should launch new Chrome and Firefox processes, which you can minimise. You can now use Testem for TDD in the usual way (see docs).
  • You can run grunt-server in another terminal at the same time.
  • In your spec runner (test/index.html), add script tags for your implementation code, which should look something like this: <script src="../app/scripts/foo.js"></script>. Script tags for spec files should look like this: <script src="specs/foo-test.js"></script>.

Optional: add the grunt-testem plugin

This lets you use Testem in CI mode during your build process. It launches browsers, runs your tests in them, and closes them afterwards.

  • Remove grunt-mocha: npm uninstall -D grunt-mocha
  • Add grunt-testem: npm install -D grunt-testem
  • In your Gruntfile...
    • remove the entire config entry for mocha, and remove the test target of connect
    • find grunt.registerTask('test'..., remove the connect:test subtask, and change 'mocha' to 'testem'
    • add this config entry:
        testem: {
            main: {
                src: [ 'testem.json' ],
                dest: 'tests.tap'
            }
        }

Edit the launch_in_ci list of browsers in your testem.json if necessary. Now try running grunt test.

Coffeescript

More steps are probably needed to get this working with Coffeescript... Instructions will appear here when I've worked it out myself. PRs welcome.

Contribute

See the contributing docs

License

BSD license