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

ac-custom-error

v1.0.0

Published

Custom NodeJS error with error code and additional info

Downloads

19

Readme

AC-Custom-Error

Extend the NodeJS error with an error code and additional information.

Node.js CI

ACErrorFromCode

This is the preferred way to use this class. You define a central library of error codes and export them to global. You can then throw the error based on that code.

Usage

const { ACErrorFromCode } = require('ac-custom-error)

// define error library
const errorCodes = {
  12345: {
    message: 'this is the error,
    solution: 'Provide optional solution to solve the error',
    stack: true // optional, if you want to log the stack
  },
  ...
}
global.errorCodes = errorCodes


// call the error
throw new ACErrorFromCode(12345)

// result in console
ACErrorFromCode: this is the error
    at STACK
  code: 12345,
  errorMessage: 'this is the error',
  solution: 'Provide optional solution to solve the error'
}

ACError

If you do not want ot use a global library of error codes, you can use ACError to still show code and additionalInfo.

Usage

Use it just like the built-in error:

  • first parameter is the actual error message as string
  • second parameter is the error code
  • third parameter is an optional object of additional information (e.g. variables clarifying the error)
  • fouth parameter is an optional object of options that can help further processing of the error

Example

const { ACError } = require('ac-custom-error')

throw new ACError('myError', 123, { id: 333 }, { stack: true })

// OUTPUT 
ACError: myError
    at STACK
  code: 123,
  errorMessage: 'myError',
  additionalInfo: { id: 333 },
  options: { stack: true }
}

How to use options

You might have an app were you would like to distinguish between soft errors (e.g. a requested ID is not available) and hard errors (that are bugs in the code). The first one should be logged as information in the code (maybe not even on ERROR level). The second one, the hard error, should probably contain as much information as possible for further debugging, so you want to log the stack as well.

// EXAMPLE soft error
throw new Error('userIdInvalid', 10223, { id: 12345 })
// will e.g. log like this
WARN | userIdInvalid | 10223 | { id: 12345 }

// EXAMPLE hard error
throw new Error('SQLinvalid', 13001, { query: 'SELECT FROM a' }, { stack: true })
// will e.g. log like this
ACError: SQLinvalid
  at SQLconnect (/pathTofile:150:10)
  ...
ERROR | SQLinvalid | 13001 | { query: 'SELECT FROM a' }

Links

License

MIT License Copyright © 2009-present, AdmiralCloud AG, Mark Poepping