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 🙏

© 2024 – Pkg Stats / Ryan Hefner

karma-mocha-webworker

v1.3.0

Published

Karma plugin which runs your mocha tests in a WebWorker

Downloads

5,286

Readme

karma-mocha-webworker

Travis CI Build Status

Karma plugin which runs your mocha tests in a WebWorker.

Using this plugin you can test your javascript code for WebWorker compatibility.

Usage

Install the module and save it as a devDependency:

npm install karma-mocha-webworker --save-dev

Instructions on how to install karma can be found here.

You will then have to configure your karma config:

module.exports = config => {
  config.set({
    // 1. Load this karma plugin
    frameworks : ['mocha-webworker'],

    // 2. Configure the files you would like karma to serve.
    //    Make sure you set `included` to `false`. Otherwise karma
    //    will execute your scripts outside of the WebWorker.
    files      : [
      {pattern: 'test/my-test-case.js', included: false},
      {pattern: 'test/more-test-cases/*.js', included: false}
    ],

    client     : {
      // 3. Configure the URLs that this plugin should execute
      //    within a WebWorker for you. These patterns are
      //    matched (using minimatch) on the `config.files`
      //    array configured in step 2.
      //    If you omit `pattern`, all URLs will be executed.
      mochaWebWorker: {
        pattern : [
          'test/my-test-case.js',
          'test/more-test-cases/*.js'
        ],
        // You can also use a SharedWorker for test execution
        // instead of the default 'Worker'
        worker: 'SharedWorker',
        // You can also pass some options to mocha:
        mocha   : {
          ui: 'tdd'
        },
        // You can also evaluate javascript code within the Worker at various stages:
        evaluate: {
          beforeMochaImport: 'self.console.log("Before the mocha script is imported")',
          beforeMochaSetup : 'self.console.log("Before mocha is setup (mocha.setup())")',
          beforeScripts    : 'self.console.log("Before your scripts are imported")',
          beforeRun        : 'self.console.log("Before your tests are run (mocha.run())")',
          afterRun         : 'self.console.log("After your tests have been run")'
        }
      }
    }
  });
};

Grep

To run only some test cases matching a given pattern, you can use:

karma start &
karma run -- --grep foo

Google Chrome Caveat

Google Chrome currently (tested up to v55) does not pass on stack information when an error occurs within a script loaded into a Web Worker (e.g. importScripts(['foo.js'])). So if your script contains a syntax error or a runtime error, the stack will point at a line within karma-mocha-webworker. You can workaround this issue by using Firefox.