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

@cd2/error-box

v0.2.1

Published

Create a consistent and descriptive errors setup for your applications.

Downloads

42

Readme

Error Box

Create a consistent and descriptive errors setup for your applications.

npm i --save @cd2/error-box

or

yarn add @cd2/error-box

Usage

Testing

You can use the jest file!


Problem

  1. It should be easy to throw consistent errors across your application
  2. You should be able to catch the exact error you want without having to rely on matching error messages
  3. Errors should be serializable so they can be used between servers and clients
  4. They should provide details for the developer to help solve the issue
  5. They should be presentable to the end user

Usage

import { createErrorType, errorIs } from "@cd2/chucker"

// create an error type
const applicationError = createErrorType("my_application")

try {
  // throw an error 
  throw applicationError("validation", "Name must be present")
} catch (e) {

  // catch only the correct errors
  if (errorIs(e, applicationError("validation"))) {

    // show the developer the error
    console.error(e)


    // show the user
    showFlashMessage(e.toHumanString())
  }
}

You can subclass errors


const applicationError = createErrorType("my_app")
const validationError = applicationError.extend("validation")
const presenceValidationError = validationError.extend("presence")


const thrownError = presenceValidationError(null, "Name must be present")

errorIs(thrownError, applicationError) // => true
errorIs(thrownError, validationError) // => true
errorIs(thrownError, presenceValidationError) // => true

Serializable

const error = applicationError(null, "Message")

const json = error.toJSON()

// send over network

const parsedError = parseError(json)