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 🙏

© 2024 – Pkg Stats / Ryan Hefner

neat-errors

v1.0.8

Published

Provide beautiful and practical error messages for your command-line tools

Downloads

2

Readme

Neat Errors for NodeJs

This is a really neat error reporter for NodeJS, featuring code extraction, stack cleaning, syntax highlighting and tweakable output out-of-the-box.

Usage

Easiest way is to require neat-errors/register at the top of your application entry point:

import "neat-errors/register";

// do your stuff here ...

If not possible in your case, then you can use the full programmatic API:

import Neat from "neat-errors"

const neat = new Neat()

process.on('uncaughtException', e => {
  console.error(neat.render(e));
  process.exit(1);
})

Unless specified manually, neat-errors will check for the following options in process.argv and adapt its behaviour accodingly:

  • --full-stack-trace: do not clean the stack trace before rendering
  • --print-all-code print a code excerpt for all call sites in the stack trace

Other than that, the following arguments can be supplied to Neat as an options object:

  • cwd: current working directory to make paths relative to.
  • printAllCode: defaults to checking process.argv for its value
  • fullStackTrace: defaults to checking process.argv for its value

Contributing

Suggestions? Found a bug? You are more than welcome to contribute! Please browse the current issues to check if someone else got to it first before submitting a new one.

Related projects

License

The MIT License