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

logged-errors

v2.8.1-4

Published

restify component (errors), extracted from "restify" with additional chainable features

Downloads

7

Readme

logged-errors

This module is a simple fork of the restify-errors with some chainable features:

  • it can log the error using an external logger (e.g. winston)
  • it can show the error stack in the body of the error
  • it can format the log output
  • it works both in Node and browser

Installation

Install logged-errors as usual:

$ npm install --save logged-errors

For browser environment add logged-error.js file in build folder.

Example

// see the examples folder

// dependencies
var LoggedErrors = require('logged-errors');

// add the stack to the body of the error
throw new LoggedErrors.NotFoundError('some error').withStack().log();

// the following statements are equivalent
throw new LoggedErrors.NotFoundError('some error').withStack().toArray().log();
throw new LoggedErrors.NotFoundError('some error').withStack(true).log();

// set a new format and a custom logger (default is console)
LoggedErrors.set({
    format: function (e) {
        return 'error occurred: ' + e.message;
    },
    logger: require('winston')
});

// change on the fly the content used for the log using the defult format
// use body (default)
throw new LoggedErrors.NotFoundError('some error').log();
// use message (set mode !== 'body')
throw new LoggedErrors.NotFoundError('some error').log('msg');

// compose a message for the error
throw new LoggedErrors.NotFoundError('some error with %s and %s', 'first parameter', 'second parameter').log();

For other information please refer to restify documentation.