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

fancy-error

v1.0.0

Published

Extended error object with context and chaining support

Downloads

10

Readme

FancyError

The FancyError object extends the native Error object with a few features:

  • a context property, allowing for passing an object along with the error message
  • a caughtError property, allowing to wrap any Error-compatible object with your own FancyError and containing the original Error in the caughtError property. This also allows you to create an error chain with allowPassthrough = false or with differently named FancyErrors.
  • a fullMessage getter, allowing to get a message containing the messages from both this and the caughtError.

Because FancyError extends Error, stack traces work as usual.

Usage

The constructor has the following signature:

constructor(
  message: string,
  caughtError?: FancyError | Error,
  context?: { [key: string]: any },
  allowPassthrough: boolean = true
): FancyError

allowPassthrough determines whether an error object with the same prototype and name is passed or wrapped.

Examples

import FancyError from 'fancy-error';

const error = new FancyError('This is an error');
const passedError = new FancyError('This error lets `error` pass through', error);
const wrappedError = new FancyError('This error wraps `error`', error, null, false);

class OtherError extends FancyError {}
const otherError = new OtherError('This is a different error so `error` is not passed', error);

console.error(passedError.fullMessage);
// "This is an error"

console.error(wrappedError.fullMessage);
// "This error wraps `error`: [FancyError] This is an error"

console.error(otherError.fullMessage);
// "This is a different error so `error` is not passed: [FancyError] This is an error"

As shown in the example above, you can also create differently named versions of this error by extending it.

throw new FancyError('This is an error', null, { exampleData: true });
import FancyError from 'fancy-error';

const error = new Error('Something went wrong somewhere!');
const fancyError = new FancyError(
  'This error wraps a system error',
  error,
  { exampleData: true }
);

console.log(fancyError.name);
// "FancyError"

console.log(fancyError.message);
// "This error wraps a system error"

console.log(fancyError.fullMessage);
// "This error wraps a system error: [Error] Something went wrong somewhere!"

console.log(fancyError.context);
// { exampleData: true }

console.log(fancyError.caughtError.message);
// "Something went wrong somewhere!"

Development

npm i
npm run test
npm run build