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

hint-errors

v1.1.2

Published

JavaScript errors done right

Readme

hint-errors

JavaScript errors done right

Install

npm install hint-errors

Usage

Standalone scripts

Add one line to the top of your entry file. The package catches the first uncaught error, shows a hint, and exits.

require("hint-errors");

const a = 10;
a = 20; // TypeError: Assignment to constant variable

When the error is fixed, the script continues normally.

Web servers

For long‑running processes, use server mode. The process stays alive after an error so a single bad request doesn't take down the whole server.

require("hint-errors/server");

const http = require("http");

const server = http.createServer((req, res) => {
  if (req.url === "/crash") {
    const user = undefined;
    console.log(user.name); // shown but server keeps running
  }
  res.end("ok");
});

server.listen(3000);

What's covered

JavaScript errors

  • TypeError – when a value is not of the expected type (e.g., reading a property of undefined)
  • ReferenceError – when a variable that doesn't exist (or hasn't been initialized) is referenced
  • SyntaxError – when the code contains invalid JavaScript syntax
  • RangeError – when a numeric value is outside the allowed range
  • URIError – when a global URI handling function is used incorrectly
  • AssertionError – when an assertion from the node:assert module fails

Node.js & OS errors

  • ENOENT – file or directory not found
  • EACCES – permission denied when accessing a file
  • EPERM – operation not permitted, common on Windows
  • EEXIST – file already exists
  • EISDIR – expected a file, got a directory
  • ENOTDIR – expected a directory, got a file
  • ENOTEMPTY – directory still has contents
  • EMFILE – too many files open at once
  • MODULE_NOT_FOUND – package not installed or path is wrong
  • ECONNREFUSED – target server isn't running
  • ECONNRESET – connection dropped by remote host
  • ETIMEDOUT – server didn't respond in time
  • EADDRINUSE – port is already taken
  • EADDRNOTAVAIL – address not available on this machine
  • EPIPE – writing to an already-closed connection
  • EAI_AGAIN – DNS lookup failed (temporary failure)
  • EHOSTUNREACH – no route to the target host

Async scenarios

  • Promise rejected with no .catch()
  • Unhandled rejection inside async/await
  • Missing await causing undefined reads

Maintainers