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

@whitehash/resolve

v0.0.2

Published

URI to HTTP URL resolution for IPFS, onchfs, and data URIs — the single source of truth for how whitehash turns content-addressed URIs into fetchable URLs.

Readme

@whitehash/resolve

Turns content-addressed URIs into fetchable HTTP URLs. Zero dependencies.

This is the single source of truth for how whitehash resolves ipfs://, onchfs://, bare CIDs, and inline URIs — preserving query strings and fragments, which fxhash artifact URIs use to carry render state (ipfs://{cid}/?fxhash=...#0x{params}).

import { createResolver, DEFAULT_IPFS_GATEWAYS } from "@whitehash/resolve"

const resolver = createResolver({
  ipfsGateways: DEFAULT_IPFS_GATEWAYS, // ["https://ipfs.io", "https://dweb.link"]
  onchfs: { mode: "service-worker" }, // same-origin /.whitehash/onchfs virtual path
})

resolver.resolveUri("ipfs://Qm.../?fxhash=oo#0xff")
// → "https://ipfs.io/ipfs/Qm.../?fxhash=oo#0xff"

resolver.resolveUri("onchfs://0xabc/index.html", { chain: "eip155:1" })
// → "/.whitehash/onchfs/eip155-1/0xabc/index.html"

await resolver.fetch("ipfs://Qm...") // tries each gateway in order

Resolution rules

| Input | Output | | --- | --- | | data: / blob: / http(s):// | returned unchanged | | ipfs://<rest> or a bare CID | <gateway>/ipfs/<rest> | | onchfs://<rest> | same-origin worker path, proxy URL, or null, according to onchfs.mode | | temp://... | null (fxhash pre-mint scheme, unsupported by design) | | unknown scheme / empty | null |

API

| Export | Purpose | | --- | --- | | defaultResolverConfig() | Public IPFS defaults with onchfs disabled until its worker assets are hosted | | resolveUri() | Resolve one URI through the first configured gateway | | resolveUriAll() | Produce the ordered fallback URL list | | fetchWithGatewayFallback() | Fetch until one configured gateway succeeds | | createResolver(config) | Bind all resolver operations to one config | | chainSlug() | Convert a chain ID for a chain-scoped onchfs path |

Service-worker mode requires @whitehash/onchfs-sw assets and registration; the static docs enable it by default. Use { mode: "proxy", baseUrl } with apps/onchfs-proxy as a fallback, or null to disable onchfs.

Attribution

Resolution rules are a dependency-free port of the fxhash proxyUrl helper (MIT), with all fxhash-hosted default endpoints removed.

Versioning

Patches preserve resolution output for supported schemes; compatible schemes/options are minor; changing existing URI semantics or return contracts is major. ESM-only; publication is not enabled yet.