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

@actualwave/type-checker-simple-reporting

v0.0.5

Published

Simple reporting functions for the TypeCheckers library

Readme

@actualwave/type-checker-simple-reporting

Three ready-to-use reporter functions for @actualwave/type-checkers and a shared message formatter.

Installation

npm install @actualwave/type-checker-simple-reporting

Usage

Pass a reporter wherever a Reporter-typed callback is expected:

import {
  ConsoleWarnReporter,
  ConsoleErrorReporter,
  ThrowErrorReporter,
} from '@actualwave/type-checker-simple-reporting';

// Log violations without stopping execution (good for development)
myChecker.setReporter(ConsoleWarnReporter);

// Hard-fail on any violation (good for tests or strict guards)
myChecker.setReporter(ThrowErrorReporter);

Reporters

| Export | Behaviour | |---|---| | ConsoleWarnReporter | Calls console.warn with a formatted message | | ConsoleErrorReporter | Calls console.error with a formatted message | | ThrowErrorReporter | Throws an Error with a formatted message (never return type) |

All three share the same Reporter signature:

type Reporter = (
  action: string,             // operation that triggered the violation, e.g. 'set', 'get'
  name: string,               // property name involved
  requiredTypeString: string, // expected type
  actualTypeString: string,   // received type
) => void;

Error message format

All reporters produce a message of the form:

<action>Error on "<name>" instead of "<requiredType>" received "<actualType>"

Example:

setError on "count" instead of "number" received "string"

constructErrorString

The underlying message builder is exported if you need to compose a custom reporter:

import {
  constructErrorString,
  Reporter,
} from '@actualwave/type-checker-simple-reporting';

const myReporter: Reporter = (action, name, required, received) => {
  analytics.track('type_violation', {
    message: constructErrorString(action, name, required, received),
  });
};

License

MIT