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

smallerr

v0.0.2

Published

A small utility for easier error handling in Typescript.

Downloads

3

Readme

smallerr

A small utility for easier error handling in Typescript.

Usage

Use the Result<Ok, Err> type to create a result. The two generics, Ok and Err, determine what types we can return.

Using the Result-type:

function maybeNumber(): Result<number, string> {
	// Use the `err()` function to easily create a new error
	if (Math.random() > 0.5) return err("Not this time!");

	return 42;
}

function handleResult() {
	const result = maybeNumber(); // type is `Result<number, string>`

	// Use the `isErr()` function to determine whether a result returned an error
	if (isErr(result)) {
		const message = result.error; // type is `string`
		return;
	}

	const ourNumber = result; // type is `number`
}

Skipping the error type with Result<Ok>

Skipping the Err-generic in Result<Ok, Err> lets us return any type of error

// `Result<number>` is equivalent to `Result<number, unknown>`, which lets us return any error
function maybeNumber(): Result<number> {
	const randomNumber = Math.random();

	if (randomNumber > 0.75) return err("Not this time!");

	// Using `err()` without an argument is equivalent to calling `err(undefined)`
	if (randomNumber > 0.5) return err();

	return 42;
}

Asynchronous results

If you're dealing with an asynchronous function, use AsyncResult<Ok, Err>

async function maybeAsyncNumber(): AsyncResult<number, string> {
	if (Math.random() > 0.5) return err("Not this time");

	await delay(500);

	return 42;
}

async function handleAsyncResult() {
	const result = await maybeAsyncNumber(); // result will be of type Result<number, string> when we await
}