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 🙏

© 2025 – Pkg Stats / Ryan Hefner

guard-promise

v0.4.0

Published

Guard Promise

Downloads

4

Readme

Guard Promise

Guard Promise let you write your async/await code in more synchronous way.

Main idea

Guard Promise always return an array of two elements: [data, err]. The first element is normal data, that you can get if your promise resolved. The second one, is the reason of promise rejection. That allows your not to use try/catch for operational errors.

Basic usage

Returning a resolved Promise

import guard from 'guard-promise';

const simpleResolveRequest = () => Promise.resolve('some data');

(async () => {
  const [data, err] = await guard(simpleResolveRequest());
  
  if (err) {
    // handle error
  }
  
  console.log(data, err); // 'some data', undefined
})();

Returning a rejected Promise

import guard from 'guard-promise';

const simpleRejectRequest = () => Promise.reject('some err');

(async () => {
  const [data, err] = await guard(simpleRejectRequest());
  
  if (err) {
    console.log(err) // 'some err'
  }
})();

NOTE: if simpleRejectRequest is async function, guard() will also handle programmer errors, because async/await function rejects the Promise it returns when function throws an exception. You can specify global predicate for Guard Promise to filter operational errors:

import { configGuard } from 'guard-promise';

configGuard({
  predicate: e => e.code
});
// guard() will be rejected if predicate returns false