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

@poppanator/assert-error

v1.0.2

Published

Assert or type assert that error is an Error

Downloads

11

Readme

assert-error

When using strict errors in TS the type of the error in the catch clause is unknown. This is a good thing since it forces you to properly handle the error.

This package provides two functions to make this error handling easier.

Install

The usual npm install @poppanator/assert-error, yarn add @poppanator/assert-error, etc...

Example

Ponder the following

try {
  // Do some funky salsa
} catch (err: unknown) {
  console.error('Error message:', err.message)
  // .................................^^^^^^^
  // It's a nono
}

Since TS doesn't know wether err is an error object or not you can't index on it.

But using assertError() you can:

import { assertError } from '@poppanator/assert-error'

try {
  // Do some funky chimichurri
} catch (err: unknown) {
  assertError(err)
  console.error('Error message:', err.message)
  // It's a Yay-Yay
}

Now TS known ist's an Error object and indexing on it is fine. If err is not an instance of (at least) Error, assertError() will throw.

To assert err is some other error than Error, you can provide the class constructor as second argument to assertError():

class MyError extends Error {
  public code = 12
}

try {
  // Do some funky pesto
} catch (err: unknown) {
  assertError(err, MyError)
  console.error('Error:', err.code)
}

Now, you may not always want something to throw in you catch clause. If that's the case you can use assumeError(), which is just a typeguard working in the same way as assertError().

assertError() is to prefer over assumeError(), but there might be situations where you just want to type-guard and not risking ending up with something throwing an error.

NOTE! assumeError() has no runtime-effect. It does nothing.

import { assumeError } from '@poppanator/assert-error'

try {
  // Do some funky gaspacho
} catch (err: unknown) {
  assumeError(err)
  console.error('Error:', err.message)

  // These two are the same thing
  assumeError<MyError>(err)
  assumeError(err, MyError)

  if (err.code) {
    console.error('Error code:', err.code)
  }
}