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

format-error

v1.0.0

Published

formats an error for display

Downloads

788

Readme

format-error

Formats an error object such that:

  • message is ignored; assumes it's in the stack
  • full stack is displayed
  • other properties on object are displayed
  • nested errors are displayed

install

npm install --save format-error

example

var format = require('format-error').format;

var error = new Error('something broke');
error.inner = new Error('some inner thing broke');
error.code = '500c';
error.severity = 'high';

var message = format(error);

console.error(message);

/*
Error:    something broke
    at Object.<anonymous> (/home/sean/demo/testium/err.js:28:13)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:902:3
inner:
  Error: some inner thing broke
    at Object.<anonymous> (/home/sean/demo/testium/err.js:29:15)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:902:3
code:     500c
severity: high
*/

api

format(error, prettyjsonOptions)

Formats an error for output. error is an Error object. prettyjsonOptions (optional) is passed directly to prettyjson.

patchError()

Permanently patches the error object such that serialization (toJSON calls) behave according to the goals of this module. This is not required unless you want JSON.stringify(error) to act somewhat like format(error) in cases where you can't control how the output is formatted directly.

This module only temporarily patches Error in order to produce the formatted output.

This can be undone by calling unpatchError().

unpatchError()

This reverts changes made to Error.prototype.toJSON by patchError().

This should only be called if you explictly called patchError.

License

MIT