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 🙏

© 2026 – Pkg Stats / Ryan Hefner

tini-tiny-reporter

v1.0.1

Published

Frontend debugging.

Readme

Tini Tiny Reporter

A zero-dependency reporter for logs, errors, failed network requests and other events which are emitted in your JS application, at one spot, for you to further analyse.

Example Usages

A simple example

Call defineReporter and all future events from that moment on will be reported to you in the report-callback.

import { defineReporter } from "tini-tiny-reporter"

defineReporter({
    report: (meta, data) => {
        // meta -> "error" | "exception", timestamp and stack
        // data -> captured log or exception
		
        // e.g. send to the central logs

        // Note: Events emitted in the callback are not reported
    },
    scopes: [
        "error",
        "exception",
    ],
})

Now, when an Error is thrown anywhere in your code, you will know. Likewise with any console.error(...) call.

// Somewhere in your code
console.error("Something unexpected happened...")

// meta -> { "scope": "error", "timestamp": "03/12/2022, 14:27:00:210", "stacktrace": [...] }
// data -> "Something unexpected happened..."

Networking Requests and Responses

tini-tiny-reporter can notify you when requests or their responses succeeded or failed with their own scopes. Fetch is supported without the need of configuration, axios needs to be passed to defineReporter:

import { defineReporter } from "tini-tiny-reporter"
import axios from "axios"

defineReporter({
    report: (meta, data) => {
        // ...
    },
    networkingFrameworks: {
        axios,
    },
    scopes: [
        "error",
        "exception",
        "unsuccessfulRequest",  // also: successfulRequest
        "unsuccessfulResponse", // also: successfulResponse
    ],
})

All Scopes

| Scope | Notes | |:------------------------|:----------------------------------------------------:| | log | console.log | | info | console.info | | debug | console.debug | | warn | console.warn | | error | console.error | | exception | throw new Error() | | online | We have re-established connectivity | | successfulRequest | Request went down as expected | | unsuccessfulRequest | Something bad happened while sending the request | | successfulResponse | Response was received as expected | | unsuccessfulResponse | Something didn't happen as planned with the response |