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

@saez-juan/result

v1.1.0

Published

Pequena utilidad para modelar resultados de operaciones con el patron "error-as-values", inspirada en `Result` de Rust. Evita excepciones para el flujo normal y hace explicito el manejo de errores.

Readme

@saez-juan/result

Pequena utilidad para modelar resultados de operaciones con el patron "error-as-values", inspirada en Result de Rust. Evita excepciones para el flujo normal y hace explicito el manejo de errores.

Instalacion

bun add @saez-juan/result

Idea principal

En vez de lanzar excepciones, las funciones retornan un objeto Result que puede ser:

  • ok(data): operacion exitosa con data.
  • err({ code, message?, details? }): operacion fallida con informacion del error.

Uso basico

import Result from "@saez-juan/result";

function divide(a: number, b: number) {
	if (b === 0)
		return Result.err({
			code: "DIV_BY_ZERO",
			message: "Cannot divide by zero"
		});
	return Result.ok(a / b);
}

const r = divide(6, 3);
if (r.isOk) {
	console.log("result:", r.value);
} else {
	console.error("error:", r.error);
}

API

Tipos exportados:

  • ResultError: { code: string; message?: string; details?: unknown }
  • SyncResult<T>: alias de Result<T> | ErrorResult
  • AsyncResult<T>: alias de Promise<Result<T> | ErrorResult>
  • ErrorResult: alias de Result<null>

Clase Result<T>:

  • Propiedades de solo lectura:
    • isOk: boolean -- indica exito
    • isErr: boolean -- indica error
    • value: NonNullable<T> -- datos cuando isOk es true
    • error: ResultError -- error cuando isErr es true
    • asError: ErrorResult -- mismo objeto, tipado como Result<null>, limpia data
  • Metodos estaticos:
    • Result.ok<D>(data: D): Result<D>
    • Result.err(err: ResultError): ErrorResult
  • Metodos de instancia:
    • clear(scope?: "data" | "error" | "all"): void -- elimina campos internos para sanitizar respuestas

Nota: evita construir Result con new. Usa Result.ok y Result.err.

Ejemplos practicos

Manejo de errores temprano:

const res = await getUser();
if (res.isErr) return res.asError; // propaga error con tipo seguro

const user = res.value;

Encadenado y sanitizacion:

const r = await createOrder(input);
if (r.isErr) return r.asError;

// Limpiar error antes de responder publicamente
r.clear("error");
return r; // solo contiene data

Uso con AsyncResult:

import type { AsyncResult } from "@saez-juan/result";

async function getPrice(id: string): AsyncResult<number> {
	try {
		const price = await service.prices.get(id);
		return Result.ok(price);
	} catch (e) {
		return Result.err({ code: "REMOTE_ERROR", details: e });
	}
}

Buenas practicas

  • Valida isOk/isErr antes de acceder a value/error.
  • Usa asError para burbujear errores sin perder tipo.
  • Utiliza clear para remover data o error al construir respuestas externas.

Hecho por Juan Saez