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

@unthrown/boxed

v5.12.0

Published

Boxed interop for unthrown

Readme

@unthrown/boxed

Boxed interop for unthrown's Result.

📖 Documentation · API Reference

pnpm add @unthrown/boxed @bloodyowl/boxed unthrown

Boxed's Result has two channels (Ok/Error) and no defect channel. Coming in, every Boxed result is an Ok or Error — never a Defect. Going out, a Defect has nowhere to live, so toBoxed forces you to triage it with onDefect — no defect is ever silently folded into your domain error type.

import { Ok } from "unthrown";
import { toBoxed, fromBoxed } from "@unthrown/boxed";
import { Result } from "@bloodyowl/boxed";

toBoxed(Ok(1), (cause) => ({ _tag: "Bug", cause })); // Result.Ok(1)
fromBoxed(Result.Ok(1)); // Result<number, never>
  • toBoxed(r, onDefect) / fromBoxed(r) — sync Result ↔ Result.
  • toBoxedFuture(ar, onDefect) / fromBoxedFuture(future) — async AsyncResult ↔ Future<Result>.

Boxed's Option has no analogue here — per unthrown's design, absence is expressed with T | undefined or Result<T, NotFound> (see fromNullable), not a dedicated Option type.

@bloodyowl/boxed is a peer dependency. (Boxed was formerly published as @swan-io/boxed, now deprecated in favour of this maintained scope.)

License

MIT © Benoit TRAVERS