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

holepunch-types

v0.2.2

Published

TypeScript type definitions for Holepunch ecosystem modules: autobase, blind-pairing, hyperswarm, z32, b4a, and more.

Readme

holepunch-types

Ambient TypeScript declarations for the Holepunch / Bare ecosystem modules that don't ship their own types, maintained as one shared package so every consumer typechecks against the same shapes.

Installation

npm install -D holepunch-types

Usage

The declarations are ambient (declare module '...'), so they need to be part of your program once. The lightest way is a single reference file included by your tsconfig.json:

// types/ambient.d.ts
/// <reference types="holepunch-types" />

Alternatively, point typeRoots at the package:

{
  "compilerOptions": {
    "typeRoots": ["./node_modules/@types", "./node_modules/holepunch-types"]
  }
}

Either way, imports of the covered modules are typed from then on:

import Corestore from 'corestore'
import Hyperswarm from 'hyperswarm'
import Hyperdrive from 'hyperdrive'

Modules covered

autobase autobee bare bare-channel bare-image-resample bare-inspector bare-media bare-rpc bare-sidecar bare-sqlite-vector bare-storage blind-pairing blind-peering brittle compact-encoding corestore hyperbee hyperblobs hyperconf hypercore hypercore-blob-server hypercore-crypto hypercore-id-encoding hypercore-storage hyperdb hyperdht hyperdispatch hyperdrive hyperschema-regen hyperswarm keet-identity-key localdrive pear-interface process-top protomux protomux-wakeup rache ready-guard rocksdb-native safety-catch scope-lock sodium-universal suspendify test-tmp watch-drive which-runtime z32

Plus a few ambient helpers: web-streams-polyfill/dist/ponyfill.mjs, Bare globals, Promise.withResolvers, and *.sql / *.wasm module declarations.

Deliberately not covered: ready-resource (the module ships its own types) and b4a (typed by @types/b4a).

Scope and accuracy

These declarations are written against real usage, not exhaustively against each module's API — treat a missing member as an invitation to add it. The long-term goal is upstreaming the stable ones into the modules themselves; this package is the shared staging ground until then.

Contributing

Open a PR against main. Keep each module's declarations in its own @types/<module>.d.ts and reference it from @types/index.d.ts.

License

See LICENSE.