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

saga-managed-error

v4.0.4

Published

Custom error class for better error handling

Downloads

2,066

Readme

Managed Error

npm version

Description

This package introduces a managed scoped Error class. It is designed to be and stay simple !!!

Here is an exemple:

{
  statusCode: 400,
  message: 'USER_REGISTER_BAD_REQUEST', // Comes from scope & status
  validations: [
    {
      field: 'email',
      message: 'missing tld'
    }, {
      field: 'firstname',
      message: 'should start with a capital'
    }
  ],
  context: {
    foo: 'bar'
  };
}

Usage

Here are the constructor arguments:

throw new ManagedError('USER_REGISTER', 400, {
  validations: [
    {
      field: 'email',
      message: 'missing tld'
    }, {
      field: 'firstname',
      message: 'should start with a capital'
    }
  ],
  context: {
    foo: 'bar'
  }
});
  1. scope required string
  2. statusCode optional number
  3. meta optional object
    1. meta.validations optional array
    2. meta.context optional object

Here is how you use it in your code.

const { ManagedError } = require('saga-managed-error');
// Or
import { ManagedError } from 'saga-managed-error';

if (!user) {
  throw new ManagedError('USER', 404);
}

if (vadlidationErrors.length > 0) {
  throw new ManagedError('USER_REGISTER', 400, { vadlidationErrors, context: req.body });
}

Valid status code

  • 400 BAD_REQUEST
  • 401 UNAUTHORIZED
  • 403 FORBIDDEN
  • 404 NOT_FOUND
  • 405 METHOD_NOT_ALLOWED
  • 406 NOT_ACCEPTABLE
  • 407 PROXY_AUTHENTICATION_REQUIRED
  • 408 REQUEST_TIMEOUT
  • 409 CONFLICT
  • 410 GONE
  • 411 LENGTH_REQUIRED
  • 412 PRECONDITION_FAILED
  • 413 PAYLOAD_TOO_LARGE
  • 414 URI_TOO_LONG
  • 415 UNSUPPORTED_MEDIA_TYPE
  • 416 RANGE_NOT_SATISFIABLE
  • 417 EXPECTATION_FAILED
  • 426 UPGRADE_REQUIRED
  • 428 PRECONDITION_REQUIRED
  • 429 TOO_MANY_REQUESTS
  • 431 REQUEST_HEADER_FIELDS_TOO_LARGE
  • 451 UNAVAILABLE_FOR_LEGAL_REASONS
  • 500 INTERNAL_SERVER_ERROR (default)
  • 501 NOT_IMPLEMENTED
  • 502 BAD_GATEWAY
  • 503 SERVICE_UNAVAILABLE
  • 504 GATEWAY_TIMEOUT
  • 505 HTTP_VERSION_NOT_SUPPORTED
  • 511 NETWORK_AUTHENTICATION_REQUIRED