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

@andrewscwei/super-error

v3.2.0

Published

Custom error for Node.js with additional properties

Downloads

58

Readme

node-super-error npm CI CD

A serializable and extendable Node.js Error with optional code, info and cause properties.

import { SuperError } from "@andrewscwei/super-error";

const cause = new Error("I am the cause");
const error = new SuperError(
  "I am the error",
  "error-code",
  { some: "info" },
  cause
);

console.log(error.name); // 'SuperError'
console.log(error.code); // 'error-code'
console.log(error.info); // { some: 'info' }
console.log(error.cause); // cause

const serialized = SuperError.serialize(error); // { 'name': 'SuperError', 'code': 'error-code', 'info': { 'some': 'info' }, 'cause': { 'name': 'Error', 'message': 'I am the cause' }, 'stack': <error_stack> }
const deserialized = SuperError.deserialize(serialized); // A `SuperError` instance equivalent to the initially created `error`.

API

Class: SuperError

A serializable and extendable Error with optional code, info and cause properties.

Property: {unknown} cause

An arbitrary cause of this error.

Property: {string} code

An arbitrary error code.

Property: {object} info

A plain object containing arbitrary info.

Method: SuperError.serialize(error)

Serializes any error into a plain object representing a SuperError.

  • @param value: unknown — Any error.
  • @returns SuperErrorObject — A plain object representing a SuperError.

Method: SuperError.deserialize(value)

Deserializes any value to a SuperError instance. SuperErrors are passed through, and Errors are converted to SuperErrors. Plain objects are deserialized to match their keys to respective SuperError properties. Strings are wrapped as the message of a SuperError and numbers are wrapped as the code of a SuperError. Everything else are wrapped as the cause of a SuperError.

  • @param value: unknown — Any value.
  • @returns SuperError — The deserialized SuperError.

Method: SuperError.from(value)

This method is an alias of SuperError.deserialize(value).

Usage

# Install dependencies
$ npm install

# Build module
$ npm run build

# Run tests against src
$ npm run unit

# Run tests against src for specific file patterns (relative to /src)
$ npm run unit --files="foo.ts"

# Run tests again built files
$ npm test

# Run tests again built files for specific file patterns (relative to /build)
$ npm test --files="foo.js"