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

@b-mo/bundle

v0.7.2

Published

runs a given dependency context

Readme

@b-mo/bundle

This module packages, loads, and resolves a dependency bundle. It allows you to easily extend dependency bundles so that you can compose applications together easily.

Install the bundle package using whatever package manager you are using these days:

npm i @b-mo/bundle

yarn add @b-mo/bundle

By default, bundle will be loaded from the current working directory, but you can override it with params

import bundle from '@b-mo/bundle'

const b = bundle({ dir:'my/other/dir' })

bundle.run(...runArgs)

API

Constructor:

const app = bundle(config);

config:

{
  dir // the directory to use as a root for the bundle
}

Load a bundle:

await app.load(config)

Loads a configuration and dependency bundle, but does not resolve or perform the injection. config is the same as the constructor and takes precedent over the config passed there.

Build a bundle:

await app.build()

Resolves and injects the dependency bundle, loading it if required, does not invoke the run() dependency.

Run a bundle

await app.run(...runArgs)

Loads and Builds a bundle (if not called before) and then invokes the run() dependency passing through any args.