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

tldr-error

v1.0.1

Published

A CLI wrapper that translates messy stack traces into readable summaries.

Readme

tldr-error 💥

Put your messy stack traces on a diet.

I built this because I got sick of missing a single comma and watching Node vomit 50 lines of node:internal garbage into my terminal. I just want to know what broke and exactly what line caused it.

tldr-error is a zero-config CLI wrapper. It intercepts your crashes, throws away the noise, and gives you a clean, readable summary of exactly what went wrong.


Before & After

CleanShot 2026-02-21 at 18 10 29


Installation

You don't even need to install it to try it. Just use npx:

npx tldr-error node your-app.js

Or, if you want it permanently on your machine, install it globally:

npm install -g tldr-error

Usage

Typing tldr-error every time is annoying. You have two better options:

Option 1: The short alias

Install globally and use the built-in 2-letter alias te:

te node index.js
te tsx server.ts
te npm run dev

Option 2: Set it and forget it (Recommended)

Add it to your package.json scripts once — then just run npm run dev like you always do:

"scripts": {
  "dev": "tldr-error nodemon index.js",
  "start": "tldr-error node index.js"
}

Normal console.logs pass through perfectly. Warnings print normally. But if your app crashes, it swallows the ugly stack trace and prints a clean red box with your exact error summary and a clickable relative file path.


Why I Built This

I'm just a dev who hates scrolling up in the terminal. I built this to scratch my own itch and save my sanity during late-night debugging sessions.

If you find a bug or a weird edge-case error (like a super specific framework syntax error) that the regex doesn't catch, please open an issue or submit a PR! I'd love to see how other people improve the parsing logic.


Contributing

  1. Fork the repo
  2. Create a branch: git checkout -b fix/your-fix
  3. Push and open a PR

License

MIT