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

balena-config-karma

v4.0.2

Published

Base balena.io Karma Test Runner configuration

Downloads

1,248

Readme

balena-config-karma

Base balena Karma Test Runner configuration

npm version dependencies ![Gitter](https://badges.gitter.im/Join Chat.svg)

Installation

Install balena-config-karma by running:

$ npm install --save-dev balena-config-karma

Setup

This module aims to provide a base Karma configuration for balena NPM modules. It's preconfigured with the following assumptions about the modern balena.io modules structure:

  • The distribution files are located in the build folder (typically created by building the TS or ES6+ sources) and have the .js extension.
  • The sources are located in src or lib folder and are in JS (ES) or TS.
  • The test specs are located in the tests folder and have the double .spec.js or .spec.ts extension.
  • The tests are importing the distribution or the source files. It's recommended to simply import the root of the project and let node decide what to do, as in the real usage scenario. It has the benefit of importing TS if the types entry is properly configured in package.json.

It supports the following features:

  • Webpack transform for the tests bundle with ES2015 support and sourcemaps.
  • Test are run in headless Chrome.
  • Mocha support.
  • CI mode enabled by default.

The module exposes a function returning the Karma configuration object that you can pass to config.set() yourself.

To get started, create a karma.conf.js in the root of your project:

var getKarmaConfig = require('balena-config-karma');
var packageJSON = require('./package.json');

module.exports = function(config) {
  var karmaConfig = getKarmaConfig(packageJSON /*, { wepbackConfig: optionalCustomWebpackConfig }*/)

  // Notice you can override the default options as you wish
  karmaConfig.logLevel = config.LOG_INFO;

  config.set(karmaConfig);
};

And run karma start.

Browsers

The local tests run in the headless Chrome.

To run them locally you need Chrome >= 59 installed.

To run them on Travis add the following lines to your .travis.yml file:

dist: trusty
sudo: false
addons:
  chrome: stable

Note: change false to required if you need sudo for your tests, see the Travis Trusty docs and the Travis container-based infrastructure docs for more details.

AppVeyor has the the proper Chrome version preinstalled.

Support

If you're having any problem, please raise an issue on GitHub and the balena team will be happy to help.