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 🙏

© 2026 – Pkg Stats / Ryan Hefner

to-result

v0.0.1

Published

Encapsulating the return value and the error coming with it

Downloads

5

Readme

to-result

Function in JavaScript could return values, in the meantime it would also throw errors if it cannot produce the caller expected value for some reasons whose details would be carried by those errors, if the errors occur then the caller should use a try-catch statement to capture the potential errors otherwise the program will be interrupted by the runtime to prevent it from running into the unpredictable state.

However try-catch is slightly inflexible since it will force the program to use an explicit control-flow branch in its catch clause. For letting the errors handling to be more flexible, this module could encapsulate the return value together with the coming error to become a boxing value called Result

Usage

npm i to-result
import { resultify } from "to-result";

async function fn() {
  // do some async work
}

const resp = await resultify(fn());
// apply the early-return pattern
if (resp.e) return;

// consuming the result
console.log(resp.r);

for the synchronous task we should convert to be its lazy-compute form:

import { resultify } from "to-result";

function fn() {
  // do some sync work
}

const resp = await resultify(() => fn());
if (resp.e) return;

for some situations we want rethrow the error:

const resp = await resultify(fn());
if (resp.e) throw resp.e;

or we could use the take method to shorten above code:

const resp = await resultify(fn());
console.log(resp.take());

since take will unboxing the result then either return the value held by the field r or rethrow the error held by the field e if it's not null, we could also use try-catch to recover the program state as normal:

const resp = await resultify(fn());
try {
  console.log(resp.take());
} catch (e) {
  console.error(e);
}