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-benchmarkjs-reporter

v1.0.0

Published

A customizable reporter for karma-benchmark.

Downloads

190

Readme

Karma Benchmark.js Reporter

A configurable Karma reporter for the karma-benchmark plugin.

Installation

npm install karma-benchmark karma-benchmarkjs-reporter --save-dev

Karma Configuration

Add benchmark to your frameworks and reporters arrays. Optionally, specify

module.exports = function(config) {
  config.set({
    // ...
    frameworks: ["benchmark"],
    reporters: ["benchmark"],
    // optional configuration object :
    benchmarkReporter: {
      colors: config.colors,
      style: style,
      decorator: "-",
      terminalWidth: 60,
      hzWidth: 4,
      hzUnits: "ops/sec",
      browserWidth: 40,
      showBrowser: false,
      showSuiteSummary: false,
      formatBenchmark: formatBenchmark,
      formatSuiteHeading: formatSuiteHeading,
      formatSuiteSummary: formatSuiteSummary
    }
  });
};

Options

colors

default: true

This value is inherited from Karma, but you can override it by specifying a boolean.

style

default:

{
  benchmark: chalk.stripColor,
  summaryBenchmark: chalk.underline,
  summaryEmphasis: chalk.bold.underline,
  browser: chalk.blue,
  decorator: chalk.cyan,
  hz: chalk.green,
  hzUnits: chalk.italic.dim,
  suite: chalk.bold.magenta
}

The style object contains the styling functions for piece of data. The default uses chalk for styling and color.

decorator

default: "-"

The decorator for the beginning of each benchmark row.

terminalWidth

default: 60

The default formatting functions attempt to match this column width for each row. There is still possibility for overflow.

hzWidth

default: 4

The default formatting functions use this to pad the formatted hz string.

hzUnits

default: "ops/sec"

The string placed after the hz as units.

browserWidth

default: 40

The default formatting functions use this to pad the browser name.

showBrowser

default: false

The default formatting functions only output the browser name if set to true. It is useful if you are benchmarking multiple browsers.

showSuiteSummary

default: false

Specify if you want to call the formatSuiteSummary function at the end of a suite.

Formatting functions

If you override the default formatting functions, you must ensure that your functions take into account the other configuration values (if you want to use them).

View the default formatting functions

/**
 * @param  {Object} benchmark the benchmark to be formatted
 * @param  {Object} browser the browser associated with the benchmark
 * @param  {Object} benchConfig the benchmarkReporter config obj
 * @return {string} the formatted benchmark
 */
var formatBenchmark = function (benchmark, browser, benchConfig) {...};

/**
 * @param  {string} suiteName name of performance suite
 * @param  {Object} browser browser object
 * @param  {Object} benchConfig benchmarkReporter config object
 * @return {string} formatted suite heading
 */
var formatSuiteHeading = function (suiteName, browser, benchConfig) {...};

/**
 * @param  {Object[]} suite array of browserBenchmarks: `{browser: {Obj}, benchmark: {Obj}`
 * @param  {Object} benchConfig benchmarkReporter config obj
 * @return {string} the formatted suite summary
 */
var formatSuiteSummary = function (suite, benchConfig) {