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

@jcbkdev/result

v0.2.0

Published

A Result type for TypeScript that makes errors explicit in function signatures

Downloads

192

Readme

@jcbkdev/result

A Result type for TypeScript. A function returns a Result<T> instead of throwing, so the possibility of failure is part of its signature.

Installation

npm install @jcbkdev/result

Usage

import { Result } from "@jcbkdev/result";

function parseAge(input: string): Result<number> {
  const age = Number(input);

  if (!Number.isInteger(age) || age < 0) {
    return Result.error(new Error(`Invalid age: ${input}`));
  }

  return Result.ok(age);
}

const result = parseAge("42");

if (result.isError()) {
  console.error(result.getError());
} else {
  console.log(result.getValue());
}

// or

if (result.isOk()) {
  console.log(result.getValue());
} else {
  console.error(result.getError());
}

Reference

Creating a result

| Method | Description | | --------------------- | -------------------------------------------------------- | | Result.ok() | Creates a successful Result<void>, with no value. | | Result.ok(value) | Creates a successful result, holding a value. | | Result.error(error) | Creates a failed result holding an Error. |

Inspecting a result

| Method | Returns | Description | | ------------ | -------------------- | -------------------------------------------------- | | isOk() | boolean | true if the result is a success. | | isError() | boolean | true if the result is a failure. | | getValue() | T \| undefined | The value of a success. undefined for a failure. | | getError() | Error \| undefined | The error of a failure. undefined for a success. |

Notes

Checking the state of a result

A success can legitimately hold undefined, null, 0, or '', so always use isOk() / isError() to determine the state, not the value returned by getValue():

// Correct
if (result.isOk()) { /* ... */ }

// Incorrect: a success holding a falsy value is treated as a failure
if (result.getValue()) { /* ... */ }

Using try/catch

A function that returns a Result should not throw. To use code that can throw, such as the URL constructor, catch the exception and return it as a failure:

function parseUrl(input: string): Result<URL> {
  try {
    return Result.ok(new URL(input));
  } catch (error) {
    // Any value can be thrown in JavaScript, so make sure an Error is returned
    return Result.error(error instanceof Error ? error : new Error(String(error)));
  }
}

Results without a value

Result.ok() with no argument returns a Result<void>. For any other type, pass the value explicitly, even if it is undefined:

function deleteUser(id: string): Result<void> {
  db.remove(id);
  return Result.ok();
}

function findUser(id: string): Result<User | undefined> {
  try {
    return Result.ok(db.get(id)); // undefined if there is no such user
  } catch (error) {
    return Result.error(error instanceof Error ? error : new Error(String(error)));
  }
}

Contributing

  1. Fork the repository.
  2. Create a branch for your change:
git switch -c feature/my-change
  1. Install the dependencies:
npm install
  1. Make your changes, then run the following and check for errors:
npm test
npm run typecheck
npm run build
  1. Commit your changes:
git commit -m "Describe your change"
  1. Push to the branch:
git push origin feature/my-change
  1. Open a pull request.

License

MIT