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

bundlebee-import

v1.0.0

Published

Peer-to-peer module imports over Hypercore

Readme

bundlebee-import

Peer-to-peer module imports over Hypercore. Like require() or import, but the modules live on the distributed web.

Uses pear-link to resolve bundle+pear:// links and bundlebee to load bundled modules from Hyperbee.

See the bundlebee-cli for release flow of pushing new bundles and getting import links.

Install

npm install bundlebee-import

Usage

const Corestore = require('corestore')
const Import = require('bundlebee-import')

const store = new Corestore('./storage')
// <-- replicate

const b4a = await Import(store.session(), 'bundle+pear://abc123...def/index.js')
const z32 = await Import(store.session(), 'bundle+pear://abc123...def/index.js')

const key = z32.encode(b4a.alloc(32, 'hi!'))

Import multiple

const Corestore = require('corestore')
const Import = require('bundlebee-import')

const store = new Corestore('./storage')
// <-- replicate

const myLib = await Import(store, 'bundle+pear://abc123...def/index.js')

Checkout specific version

Currently older versions of a Bundle can be checked out by choosing the Hypercore length where to checkout at:

// checkout at length 3
const myLib = await Import(store, 'bundle+pear://0.3.abc123...def/index.js')

console.log(myLib) // module.exports from the remote module

How it works

  1. A bundle+pear:// link is parsed to extract the Hypercore drive key and module pathname.
  2. A BundleBee instance connects to the drive using the provided Corestore.
  3. The target module is loaded and its exports are returned — just like require().

Modules are distributed as bundles stored in a Hyperbee, replicated over the Hypercore protocol. This means they are content-addressed, cacheable, and available from any peer on the swarm.

API

const exports = await Import(store, link, [opts])

Import a module from a bundle+pear:// link.

  • store — A Corestore instance for storage and replication.
  • link — A bundle+pear:// link string pointing to the bundled module (e.g. bundle+pear://<key>/path/to/module.js).
  • opts — Optional. Forwarded to BundleBee and the module loader.

Returns a promise that resolves to the module's exports.

License

Apache-2.0