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

formatted-error

v1.0.1

Published

Allows you to use placeholders in your errors.

Downloads

7

Readme

Formatted Errors

Build Status Contributions Welcome

This is a JavaScript Error object that lets you use placeholders in your error message, then it replaces them with the values supplied in the parameters object.

What is the purpose?

This project might seem silly or downright stupid at first, especially since you can already put values directly into your error like this...

throw new Error(`Error ${code} occurred.`)

That was pretty simple!

There is however this really annoying project where we can't hard-code our error messages because we don't know what the error message is, or even what the parameters are, until after the configuration is loaded.

So that's why we created this error....

Error Properties

| Argument | Type | Description | |----------|--------|-------------------------------------------------------------------| | message | string | The final error message with the placeholders replaced. | | original | object | The original error message with the placeholders intact. | | params | object | Nested object containing the values for the placeholders. |

Creating a Formatted Error

Right now the formatted errors use curly braces { and } to encapsulate the placeholders. The value inside the curly braces must map to a property on our parameters object. Below our placeholder {name} is being mapped to the param.name property.

const FormattedError = require('formatted-error');

try{
    
    let message = "{name}, we have a problem!";
    let params = {
        name: 'Houston'
    };
    
    throw new FormattedError(message, params);
    
} catch (error) {
    
    // Outputs "Houston, we have a problem!"
    console.log(error.message); 
}

Using Nested Objects as Parameters

This time we are going to provide a nested object for the parameters. In order to get that value, our placeholder will want to separate the object levels with a period {user.profile.nickname}. Then our error knows the value can be found at params['user']['profile']['nickname'].

const FormattedError = require('formatted-error');

try{
    
    throw new FormattedError("Hello {user.profile.nickname}!", {
        user: { profile: { nickname: 'Captain Awesome' } }
    });
    
} catch (error) {
    
    // Outputs "Hello Captain Awesome!"
    console.log(error.message); 
}

Dealing with Arrays

Arrays can serve many purposes, which is why their contents don't always convert to string, but when all the values are primitives (strings, numbers, booleans), then we know that we can join them together...

const FormattedError = require('formatted-error');

try{
    
    throw new FormattedError("Here are a few of my favorite things {primitives}!", {
        primitives: ['pizza', 42, true]
    });
    
} catch (error) {
    
    // Outputs "Here are a few of my favorite things pizza, 42, true!"
    console.log(error.message); 
}

If a placeholder's value is an array of complex functions and objects then the placeholder will be ignored completed, as we haven't decided how to handle dealing with those yet. Since these errors are meant to use messages and parameters created by the end-user, we don't exactly want to execute any functions they supply.

const FormattedError = require('formatted-error');

try{
    
    throw new FormattedError("Here is my {ignore} placeholder!", {
        ignore: [
            { name: 'Joseph' },
            { name: 'Jacob' },
            { name: 'Schmidt' },
        ]
    });
    
} catch (error) {
    
    // Outputs "Here is my {ignore} placeholder!"
    console.log(error.message); 
}