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

v0.2.5

Published

A better html reporter for karma

Downloads

26

Readme

karma-dhtml-reporter

NPM

A better html reporter for karma

ChangeLog

0.2.5

  • Fixed Error caused in recent karma version.

0.2.4

  • Added openReportInBrowser option to open the report in the browser after the test concludes.

0.2.3

  • Fixed bug where when singleRun mode is off, it renders an aggregated list leading to incorrect

0.2.2

  • Added Badge

0.2.1

  • Added SemanticUi Icons to the stack
  • Icons for success/failure indicators on tests
  • exclusiveSections config setting
  • More Prominent error logging

Install

npm install karma-dhtml-reporter

Use

module.exports = function (config) {
    config.set({

          ...
        dhtmlReporter: {
            'outputFile' : 'output/file/location/report.html',
            'exclusiveSections': true,
            'openReportInBrowser': false
        },

        reporters: ['DHTML'],

        plugins: [

               ...

            'karma-dhtml-reporter'
        ]
    })
}

Config

outputFile [dhtml.html]

This indicates where you want the output file to be generated

exclusiveSections [true]

If true, it only allows one section amidst its siblings to be open at a given time. Disable to allow opening multiple sections.

openReportInBrowser [false]

If true, it will open the generated report in your default browser. (uses open package from npm - check for supported platforms)

Screenshot

Screenshot