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

kind-regards

v0.0.4

Published

Teaching my Node APIs some manners.

Readme

Kind Regards,

... is the CLI output resulting from the following:

import { Reporter } from "kind-regards";
import { join } from "path";

const report = Reporter({
  verbose: true,
  debug: true,
  documentation: join(__dirname, "DIAGNOSTICS.md"),
});

report.diagnostic({
  category: "warning",
  message: "Warning Log",
  file: __filename,
});

report.diagnostic({
  category: "error",
  message: "Recoverable error log",
  file: __filename,
  recoverable: true,
});

report.info("Info log");
report.verbose("Verbose-mode only log");
report.success("Success log");

const a = {
  b: {
    c: {
      d: () => console.log("e"),
    },
  },
};
// @ts-ignore
a.b.c.f = a;
report.debug(a);

report.diagnostic({
  category: "error",
  message: "Unrecoverable error log",
  file: __filename,
});

Why?

Because it's kind to...

  • be concise when displaying varying kinds of logs to users.
  • offer users silent, verbose, and debug modes.
  • offer serialization, highlighting, and pretty-printing data (circularities included).

Between warnings, errors, one-off console logs, verbose/debug-mode logs, circular-object printing, and their related documentation... there's a lot of complexity to manage. kind-regards takes care of this complexity.

Installation

npm i kind-regards

Instantiation

import { Reporter } from "kind-regards";

const report = Reporter();

Configuration Options

Reporter accepts an optional object with the following properties:

| Key | Type | Default | Description | | :-- | :-- | :-- | :-- | | documentation | string | Falsy | undefined | Relative path to API-wide documentation. | | silent | boolean | Falsy | undefined | Disables all logging (which is especially useful in publicly-accessible CI/CD environments). | | verbose | boolean | Falsy | undefined | When false, report.verbose logs will be hidden. | | debug | boolean | Falsy | undefined | When false, report.debug logs will be hidden. |

For instance...

import { Reporter } from "kind-regards";
import { join } from "path";

const report = Reporter({
  verbose: true,
  debug: true,
  documentation: join(__dirname, "../README.md"),
});

make sure––when publishing––to include the referenced documentation in your package

Methods

... look at the type definitions ;)