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

cano-cube-error

v2.0.1

Published

Load error defined and use them with cano-koa microframework

Downloads

20

Readme

Cube Error for Cano Koa

Build clases for handling errors defined in a JSON file for the cano-koa microframework. This is the json structure that represents the error group for users:

{
  "opts": {
    "unknownError": {
      "code": "UserUnknownError",
      "description": "Unknown error. Please contact the API provider for more information.",
      "status": 500
    },
    "className":"UserError"
  },
  "notFound": {
    "status": 404,
    "description": "User not found."
  },
  "emailExist": {
    "status": 400,
    "description": "The email already exist in system."
  }
}

The first level of the object represents the possible errors (code error), except for the opts field. This field allows you to add settings for the class to be built. So far the options unknownError and className can be configured. If the opts field is not specified, the following default will be set:

{
  "code": "UnknownError",
  "description": "Unknown error. Please contact the API provider for more information.",
  "status": 500
}

If the className field is not specified, the name of the file will be taken as the class name.

At the next level of the json structure, for each error a description field must be defined that explains the error and a status field that will be an HTTP status to respond to the query affected by error:

{
    "description": "User not found.",
    "status": 404
}

If some of these two fields is not defined, the fields defined in opts.unknownError will be taken. If these are also not defined, the default fields of the quark will be taken.

Each built class is inserted as global. The classes will have as name, the name of the json file where their errors were defined.

To generate a new error, you must only create a new object of some of the classes and pass by parameter the error code and the native error (error object or string) that occurred:

throw new UserError('emailExist', 'This is native error.');

or

try {
    ...
} catch (err) {
    throw new UserError('emailExist', err);
}

Resulting object

{
    original: [Error],
    content: {
        code: 'emailExist',
        description: 'The email already exist in system.'
    },
    fullContent: {
        code: 'emailExist',
        description: 'The email already exist in system.',
        message: 'This is native error.'
    },
    status: 400
}

The method handler

This static method allows you to transform errors (not defined in the errors folder) of the Javascript Error class and convert them to an unknown CanoError error.

try {
    throw new Error('this is an error.');
} catch (err) {
    UserError.handler(err);
}

This method configures an error object of unknown type, based on the options defined in the json file of the class in question called by the method.

The CanoError base class configures the object of unknown type with the default values of the cube. This can be avoided by passing an options object as a second parameter. The options follow the same structure of the unknownError field of the json files.

try {
    throw new Error('this is an error.');
} catch (err) {
    const opts = {
        "code": "MyUknownError",
        "description": "Unknown error.",
        "status": 500
    };
    CanoError.handler(err, opts);
}

More information in the test.