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

make-joiful-errors

v0.1.0

Published

A custom error formatter for joi that objectifies the error response for readability

Downloads

19

Readme

make-joiful-errors

Return joi errors as objects to help with readability.

Designed for use against large schemas in conjunction with the { abortEarly: false } joi.validate option, but can be used by anyone wanting to format joi errors differently.

Tested with [email protected]

Install

npm i make-joiful-errors

Usage

The module exports two functions, joiErrorFormatter & joiValidateWrapper.

Both take an ErrorOptions argument.

/**
 * Options that can be passed to joiErrorFormatter
 */
interface ErrorOptions {
  showErrorIndexes?: boolean;
}

showErrorIndexes declares whether to return array indexes of each joi ValidationError. Setting { showErrorIndexes: false } prevents the same ValidationError being returned multiple times (see bottom of readme for examples).

import { joiErrorFormatter, joiValidateWrapper } from 'make-joiful-errors'

// ... all of your standard joi schemas here ...

/**
 * Use the error formatter directly when there is an error
 */

// Standard joi
const res = joi.validate(data, schema, validationOptions);

// If there's an error, pass it into the joiErrorFormatter
if (res.error) {
  joiErrorFormatter(res.error, { showErrorIndexes: false });
}

// ---- OPTIONAL WRAPPER

/**
 * Call the wrapper as you would joi.validate with an extra argument for the error formatter
 */
const res = joiValidateWrapper(data, joiSchema, joiValidateOptions, { showErrorIndexes: true })

Response comparison:

joi 14.3.1

// joiOptions = { abortEarly: false }
ValidationError: child "myObj" fails because ["myObj" at position 0 fails because [child "myKey" fails because ["mySubKey" is not allowed], "myKey" is not allowed, "myKey" is not allowed], "myObj" at position 1 fails because [child "myKey" fails because ["mySubKey" is not allowed], "myKey" is not allowed, "myKey" is not allowed], "myObj" at position 2 fails because [child "myKey" fails because ["mySubKey" is not allowed], "myKey" is not allowed, "myKey" is not allowed], "myObj" at position 3 fails because [child "myKey" fails because ["mySubKey" is not allowed], "myKey" is not allowed, "myKey" is not allowed], "myObj" at position 4 fails because [child "myKey" fails because ["mySubKey" is not allowed], "myKey" is not allowed, "myKey" is not allowed], "myObj" at position 5 fails because [child "myKey" fails because ["mySubKey" is not allowed], "myKey" is not allowed, "myKey" is not allowed]]

joiErrorFormatter { showErrorIndexes: false }

// De-duplicates the same type of validation error
Error: {
    "myObj.myKey.mySubKey is not allowed": {
        "currentValue": true,
        "currentType": "boolean"
    },
    "myObj.myKey2 is not allowed": {
        "currentValue": 5,
        "currentType": "number"
    },
    "myObj.myKey3 is not allowed": {
        "currentValue": null,
        "currentType": "object" // This is the node response for typeof null
    }
}

joiErrorFormatter { showErrorIndexes: true }

// Will show the same type of validation error multiple times
Error: {
"myObj.[0].myKey.mySubKey is not allowed": {
        "currentValue": true,
        "currentType": "boolean"
    },
    "myObj.[0].myKey2 is not allowed": {
        "currentValue": 5,
        "currentType": "number"
    },
    "myObj.[0].myKey3 is not allowed": {
        "currentValue": null,
        "currentType": "object"
    },
    "myObj.[1].myKey.mySubKey is not allowed": {
        "currentValue": true,
        "currentType": "boolean"
    },
    "myObj.[1].myKey2 is not allowed": {
        "currentValue": 5,
        "currentType": "number"
    },
    "myObj.[1].myKey3 is not allowed": {
        "currentValue": null,
        "currentType": "object"
    },