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

ts-outcome

v0.1.0

Published

A small set of Typescript utils to represent success / failure in a more sane way than throwing errors

Readme

ts-outcome

A small set of Typescript utils to represent success / failure in a more sane way than throwing errors.

Motivation

When working in large TS codebases with colleagues in the past, we've been bitten in deep stacks where some function threw, but someone forgot to handle that with a try-catch. TS doesn't provide a way to document what errors could be thrown by a function. This package draws inspiration from Rust's Result type and Go's explicit error handling to make error handling explicit in TS.

Go from:

function parseJson(jsonString: string): UserData {
  try {
    return JSON.parse(jsonString);
  } catch (e) {
    throw new Error('Failed to parse JSON');
  }
}

// You need to remember that parseJson can throw an error and try-catch it.
try {
  const userData = parseJson('{"name": "Alice", "age": 30}');
  console.log('User name:', userData.name);
} catch (error) {
  // `error` type is unknown at this point in the code.
  console.error('Failed to parse user data:', error);
}

To:

function parseJson(jsonString: string): Outcome<UserData> {
  try {
    return makeSuccess(JSON.parse(jsonString));
  } catch (e) {
    return makeError(new Error('Failed to parse JSON'));
  }
}

const result = parseJson('{"name": "Alice", "age": 30}');
if (result.isSuccess) {
  // Type narrowing here ensures result.value is UserData type.
  console.log('User name:', result.value.name);
} else {
  // Type narrowing here ensures result.error is an instance of the Error class.
  console.error('Failed to parse user data:', result.error);
}

Installation

npm install ts-outcome

Usage

TBD

API

TBD