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 🙏

© 2025 – Pkg Stats / Ryan Hefner

toxic-reporter

v1.0.8

Published

Hello! I'm just a silly little module, which will help people and QA's to make more colorful html report after running all the tests.

Readme

toxic-reporter

Hello! I'm just a little module, which will help people and QA's to make more colorful html report after running all the tests.

What I do?

  • generate an HTML file, which contains of success or error messages. You can see an example if you copy the report folder to your computer and open 'report.html' in your browser

How to use me?

  1. install the latest version of Toxic reporter by npm in you console:
    $ npm install toxic-reporter.
  2. import class Report in your script like. const { Report } = require('./app');
  3. Make a new report folder for your tests and name the report file:
    const report = new Report('reportfolder', 'toxic-report.html').
  4. Add error or success messages to your new report, like:
    report.addSuccess('Yay, it worked!'); // adds green line which tells that test have passed.
    report.addError('Oops, something is wrong', 'Here is a stacktrace', 'optional-image.png'); /* when you add an error message, you can also give diagnostical info like a stacktrace and a screenshot, which is very useful if you are running UI test with Puppeteer/Playwright */ report.addMessage('I am a line with no colors'); // adds just a text without any coloring.
  5. When all tests have passed, add a finishing part to your report:
    report.addEnding(); // it is not nessesary but it's a good style.
  • you can also see an example of usage in 'usingExample.js' with command 'node usingExample.js'.