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

errorplain

v0.1.0

Published

Turn ugly JavaScript errors into useful explanations — property chains, JSON positions, missing modules.

Readme

errorplain

Turn ugly JavaScript errors into useful explanations.

One small problem. One obvious API. Very little setup. Immediate value.

TypeError: Cannot read properties of undefined (reading 'avatar')

technically correct — and still useless. Which object was undefined? Which property chain failed? Where do you fix it?

Install

npm i errorplain

Usage

import { explain, printError } from "errorplain";

try {
  renderUser();
} catch (error) {
  console.log(explain(error));           // full explanation as text
  // or
  printError(error);                     // prints via console.error
}

What you get

Tried to read "avatar" from undefined

The code accessed property "avatar" on a value that is undefined.
Common causes:
  · async data not loaded yet (the object came back undefined)
  · optional field actually missing on this sample
  · wrong variable name
Fix: optional chaining, ensure data arrived before render, or guard early.

Location: src/components/Profile.tsx:41:28

Structured result

const { kind, headline, details, location } = explain(error);
// kinds: TypeError | SyntaxError | ModuleNotFound | FileNotFound
//        | ConnectionRefused | Network | RangeError | Unknown

Covered MVP patterns

| original | explanation | |---|---| | Cannot read properties of undefined (reading 'x') | missing object + property named, causes list | | Unexpected token } in JSON at position 82 | Invalid JSON + position + causes | | Expected double-quoted property name in JSON at position 16 (Node 25 style) | same, adapted | | Cannot find module '@/services/user' | relative/absolute hint + closest files on disk | | ENOENT: no such file or directory, open 'x' | file not found + cwd note | | connect ECONNREFUSED 127.0.0.1:5432 | nothing listening at host:port | | fetch failed (+ cause) | network failure with the low-level cause |

Unmatched errors fall back to the raw message — never worse than before.

API

explain(error)      // structured explanation with .toString()
formatError(error)  // plain string
printError(error)   // console.error the explanation

Zero dependencies. ESM + CJS + .d.ts. Node >= 18.

License

MIT