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

v1.0.0

Published

A Karma plugin. Test CommonJS modules.

Downloads

12,537

Readme

Build Status

karma-commonjs

A Karma plugin that allows testing CommonJS modules in the browser.

Browserify

If you're using Browserify to compile your projects, you should consider karma-browserify which runs Browserify directly. The cost is slightly slower builds (but not too bad, thanks to an incremental loading algorithm) and somewhat messier stack traces. The benefit is support for the full Browserify API and automatic discovery of 'require'd files.

karma-commonjs

  1. Provides a lightweight commonjs wrapper around your code
  2. Supports Node's require algorithm
  3. Only reloads files that change
  4. Provides stack traces that point to your original files
  5. Requires you to specify files in the Karma config file

karma-browserify

  1. Creates a temporary bundle using Browserify
  2. Supports the full Browserify API, including transforms, plugins, and shims for Node globals
  3. Uses watchify to perform incremental rebuilds
  4. Can use source maps to provide useful stack traces
  5. Automatically includes required files

Installation

The easiest way is to keep karma-commonjs as a devDependency:

npm install karma-commonjs --save-dev

which should result in the following entry in your package.json:

{
  "devDependencies": {
    "karma": "~0.10",
    "karma-commonjs": "~0.2"
  }
}

Configuration

// karma.conf.js
module.exports = function(config) {
  config.set({
    frameworks: ['jasmine', 'commonjs'],
    files: [
      // your tests, sources, ...
    ],

    preprocessors: {
      '**/*.js': ['commonjs']
    }
  });
};

Additionally you can specify a root folder (relative to project's directory) which is used to look for required modules:

commonjsPreprocessor: {
  modulesRoot: 'some_folder'  
}

When not specified the root folder defaults to the karma.basePath/node_modules configuration option.

For an example project, check out Karma's client tests.


For more information on Karma see the homepage.