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

smart-error-explainer

v0.1.0

Published

Turn raw Node.js errors into human-friendly explanations and suggested fixes.

Downloads

7

Readme

smart-error-explainer

Turn raw Node.js errors into human-friendly explanations and suggested fixes. Works as a small library and a CLI.

  • Library API: explain(error) returns a structured explanation object
  • CLI: smart-error reads from stdin, a file, or --error "..."

Install

npm i smart-error-explainer
# or
pnpm add smart-error-explainer
# or
yarn add smart-error-explainer

For the CLI:

npx smart-error-explainer # via npx (once published)
# or if installed globally
npm i -g smart-error-explainer
smart-error --help

Usage (Library)

const { explain } = require('smart-error-explainer');

try {
  require('expressx');
} catch (err) {
  const info = explain(err);
  console.log(info.title);
  console.log(info.explanation);
  console.log(info.fixes);
}

Usage (CLI)

  • Pipe an error:
some-command 2>&1 | smart-error
  • From a file:
smart-error --file error.log
  • From a string:
smart-error --error "Cannot find module 'express'"
  • JSON output:
smart-error --error "ReferenceError: foo is not defined" --json

Output shape

interface Explanation {
  title: string;
  explanation: string;
  probableCauses: string[];
  fixes: string[];
  references: { label: string; url: string }[];
  confidence: number; // 0..1
  matchedRule: string | null; // e.g. "node.module_not_found"
  raw: string; // normalized input
}

Supported patterns (initial)

  • MODULE_NOT_FOUND / "Cannot find module 'x'"
  • EADDRINUSE (port in use)
  • EACCES (permission denied)
  • ENOENT (file not found)
  • SyntaxError (common)
  • ReferenceError (not defined)
  • TypeError (x is not a function)
  • Network: ECONNREFUSED, ETIMEDOUT

Contributions for more rules are welcome. See src/index.js RULES for examples.

Roadmap

  • More granular rules (Next.js, Express, TypeScript, Prisma, Playwright, etc.)
  • Confidence scoring improvements
  • Links to official docs and curated blog posts for each rule
  • Optional telemetry-free heuristics (e.g., check for package.json deps)

Local development

# run CLI help
npm start

# quick demo
node -e "require('./src/index').demo()"

# try CLI with a sample error
node -e "console.error('Error: Cannot find module \'express\'')" | node bin/smart-error.js

Publishing to npm

  1. Update package.json version
  2. Ensure files are correct: files field includes src/, bin/, index.d.ts, LICENSE, README.md
  3. Login and publish:
npm login
npm publish --access public

Package name: smart-error-explainer.

License

MIT © Harsh Patel