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

@micheldever/attempt

v1.1.0

Published

Simple try-catch-finally code block handler

Downloads

3

Readme

Installation

This package is distributed via npm. You can install it as a dependency in your project by running:

yarn add @micheldever/attempt

Usage

You can use either the synchronous or asynchronous method to remove any regular try-catch calls within your codebase. Both method return a tuple containing an error object and a result. If the asserted callback does not throw an error then the error index will be null. Equally, if an error is thrown then the result index will be null instead.

Synchronous

import { attempt } from '@micheldever/attempt';

const [error, result] = attempt(() => myThrowableMethod());

Asynchronous

import { attemptAsync } from '@micheldever/attempt';

const [error, result] = await attemptAsync(() => myAsyncThrowableMethod());

Custom Error Handler

Both methods can also take an optional error handler as a second parameter. This handler will only be called if the asserted callback throws an error.

function customErrorHandler(error: Error) {
  console.log(error);
}

const [error, result] = attempt(() => myThrowableMethod(), customErrorHandler);
const [error, result] = await attemptAsync(() => myAsyncThrowableMethod(), customErrorHandler);

Using Confirm

If you need to assert that a condition is true, and throw and error if it is not, you can use the confirm utility function to do so. This accepts a boolean condition as its first parameter and either a basic string error message, or a custom error object as its second.

When providing just a basic error message the resulting error will be thrown as a TypeError.

import { confirm } from '@micheldever/attempt';

const creature = {
  name: 'dragon',
  type: 'fire',
};

confirm(creature.name === 'dragon', 'creature must be a dragon');
confirm(creature.name === 'dragon', new MyCustomError('creature must be a dragon'));

When using the confirm method in a TypeScript environment, it also provides the additional benefit of automatically narrowing the type of a given variable.

const value: string | number = await fetchSomeDynamicValue();
// TypeScript thinks `value` could be either a string or a number

confirm(typeof value === 'string', 'value must be a string');
// TypeScript knows `value` must be a string