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-fuse-box

v1.1.0

Published

Use fuse-box with karma

Downloads

10

Readme

Install

With npm

npm install --save-dev karma-fuse-box

With yarn

yarn add --dev karma-fuse-box

Usage

karma.conf.js

const path = require("path");

module.exports = config => {
  config.set({
    files: [
      // all files ending in "_test"
      { pattern: "test/*_test.js", watched: false },
      { pattern: "test/**/*_test.js", watched: false }
      // each file acts as entry point for the fusebox configuration
    ],

    preprocessors: {
      // add FuseBox as preprocessor
      "test/*_test.js": ["fusebox"],
      "test/**/*_test.js": ["fusebox"]
    },

    fusebox: {
      // FuseBox configuration
      homeDir: path.join(process.cwd(), "test/")
    },

    // for TypeScript
    mime: {
      "text/x-typescript": ["ts", "tsx"]
    }
  });
};

Alternative Usage

This configuration is more performant, but you cannot run single test anymore (only the complete suite).

The above configuration generates a FuseBox bundle for each test. For many test cases this can result in many big files.

The alternative configuration creates a single bundle with all test cases.

karma.conf.js

files: [
  // only specify one entry point
  // and require all tests in there
  'test/index_test.js'
],

preprocessors: {
  // add fusebox as preprocessor
  'test/index_test.js': [ 'fusebox' ]
},

// additional arithmetic instructions needed
// unlike WebPack FuseBox will not recognize files only by source code
fuseboxInstructions: '+ test/**_test.js',

test/index_test.js

// use fusebox runtime API to load spec files
FuseBox.import("./**_test");

Options

Full list of options you can specify in your karma.conf.js

fusebox

FuseBox configuration (fuse.js)

fuseboxInstructions

String with additional instructions for file bundling

License

MIT