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

@alt-stack/result

v1.5.1

Published

Type-safe Result type for explicit error handling inspired by Effect-TS

Readme

@alt-stack/result

Typed success and expected failure values for Altstack and standalone TypeScript applications.

Install

pnpm add @alt-stack/result

The implementation has no runtime dependency. Its manifest declares Zod 4 as an optional peer for ecosystem compatibility.

Quickstart

import {
  TaggedError,
  err,
  isErr,
  ok,
  type Result,
} from "@alt-stack/result";

class MissingUserError extends TaggedError<"MissingUserError"> {
  readonly _tag = "MissingUserError" as const;

  constructor(readonly userId: string) {
    super(`User ${userId} was not found`);
  }
}

function loadUser(id: string): Result<{ id: string }, MissingUserError> {
  return id === "u_123" ? ok({ id }) : err(new MissingUserError(id));
}

const result = loadUser("missing");
if (isErr(result)) {
  console.error(result.error._tag, result.error.userId);
} else {
  console.log(result.value.id);
}

A Result has an outer _tag of "Ok" or "Err". A failure carries an actual Error instance with a string _tag. A readonly literal tag is not required for ResultError conformance, but it enables exhaustive narrowing of an error union. Supplying TaggedError<"MissingUserError"> makes the base class enforce that exact literal.

Public surface

  • construction and guards: ok, err, isOk, isErr;
  • composition: map, flatMap, mapError, catchError;
  • extraction and matching: unwrap, defaults, match, and fold;
  • async boundaries: fromPromise, tryCatch, and tryCatchAsync;
  • collections and observation: all, firstOk, tap, and tapError;
  • tagged errors and inference helpers: TaggedError, ResultAggregateError, isResultError, assertResultError, and the exported helper types.

Documentation

Development

From the repository root:

pnpm --filter @alt-stack/result exec vitest run src/result.spec.ts
pnpm --filter @alt-stack/result check-types
pnpm --filter @alt-stack/result build