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

modern-errors-switch

v4.0.0

Published

`modern-errors` plugin to execute class-specific logic

Downloads

564

Readme

Node Browsers TypeScript Codecov Minified size Mastodon Medium

modern-errors plugin to execute class-specific logic.

This adds BaseError.switch() to wrap an error according to its class.

Hire me

Please reach out if you're looking for a Node.js API or CLI engineer (11 years of experience). Most recently I have been Netlify Build's and Netlify Plugins' technical lead for 2.5 years. I am available for full-time remote positions.

Example

Adding the plugin to modern-errors.

import ModernError from 'modern-errors'

import modernErrorsSwitch from 'modern-errors-switch'

export const BaseError = ModernError.subclass('BaseError', {
  plugins: [modernErrorsSwitch],
})
// ...

Wrapping an error's message according to its class.

try {
  // ...
} catch (error) {
  throw BaseError.switch(error)
    .case(InputError, 'The input was invalid.')
    .case(DatabaseError, 'Bug at the database layer.')
    .default('Unknown error.')
}

Install

npm install modern-errors-switch

This package works in both Node.js >=18.18.0 and browsers.

This is an ES module. It must be loaded using an import or import() statement, not require(). If TypeScript is used, it must be configured to output ES modules, not CommonJS.

API

modernErrorsSwitch

Type: Plugin

Plugin object to pass to the plugins option of ErrorClass.subclass().

BaseError.switch(error)

error: unknown
Return value: Switch

Apply logic according to error's class. This must be chained with .case() and end with .default().

Although error should be an Error instance most of the times, it can be of any type. However, the final value returned by .default() is always an instance of BaseError or a subclass of it.

Switch.case(condition, ...effects)

condition: Condition
effect: Effect
Return value: Switch

If error matches the condition, apply the effects. 0, 1 or multiple effects can be applied.

Switch.default(...effects)

effect: Effect
Return value: BaseError

If none of the .case() statements matched, apply those default effects.

Condition

The condition can be:

  • An error class, matched with instanceof
  • An error name string
  • A filtering function taking the error as argument and returning a boolean

Effect

Each effect can be:

Usage

Wrap error message

BaseError.switch(error)
  // If `InputError`, then appends the following message
  .case(InputError, 'The input was invalid.')
  // If the message ends with `:` or `:\n`, it is prepended instead
  .case(DatabaseError, 'Bug at the database layer:')
  // Empty error messages are ignored
  .default('')

Convert error classes

// Convert `TypeError` class to `InputError`, etc. or default to `UnknownError`
BaseError.switch(error)
  .case(TypeError, InputError)
  .case(URIError, ClientError)
  .default(UnknownError)

Wrap error options

BaseError.switch(error)
  // If `DatabaseError`, add options for other plugins like `modern-errors-bugs`
  .case(DatabaseError, { bugs: 'https://github.com/my-name/my-project/issues' })
  .default()

Map error

BaseError.switch(error)
  // If `DatabaseError`, adds `error.databaseUrl`
  .case(DatabaseError, (error) => {
    error.databaseUrl = databaseUrl
    return error
  })
  .default()

Multiple effects

BaseError.switch(error)
  // 0 effects
  .case(TypeError)
  // Multiple effects
  .case(URIError, ClientError, 'Invalid URI.', {
    bugs: 'https://github.com/my-name/my-project/issues',
  })
  .default(UnknownError)

Custom condition

BaseError.switch(error)
  // If `error.type` is `database`, append the following message
  .case((error) => error.type === 'database', 'Bug at the database layer.')
  .default()

Unknown errors

// Any `error` can be wrapped, even if it is not an `Error` instance
try {
  throw null
} catch (error) {
  // Therefore the filtering and mapping functions' argument might be anything
  throw BaseError.switch(error)
    .case(
      (error) => error instanceof Error && error.type === 'database',
      'Bug at the database layer.',
    )
    .default((error) => {
      if (error instanceof Error) {
        error.type = 'other'
      }

      return error
    })
}

Related projects

Support

For any question, don't hesitate to submit an issue on GitHub.

Everyone is welcome regardless of personal background. We enforce a Code of conduct in order to promote a positive and inclusive environment.

Contributing

This project was made with ❤️. The simplest way to give back is by starring and sharing it online.

If the documentation is unclear or has a typo, please click on the page's Edit button (pencil icon) and suggest a correction.

If you would like to help us fix a bug or add a new feature, please check our guidelines. Pull requests are welcome!