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 🙏

© 2024 – Pkg Stats / Ryan Hefner

bundbi

v1.1.10

Published

bundle builder for browserify

Downloads

35

Readme

bundbi

bundle builder for browserify

Build Status

Install


# to get the cli
$ npm install -g bundbi

$ bundbi [build name]

Usage

In your package.json's browserify config add a build object. Each value in build is the config for building a bundle. You and supply The same browserify configs detailed here.

A build also accepts these attributes:

  • main : (required) path to main entry point for browserify to build from
  • outfile : (required) file where the bundle is written to
  • external: an array of external modules. see here
  • watch : enables watchify on the main file

Any config can be added directly under the the browserify key to provide configuration for all builds. These can be overridden in each build config.

External builds

If an external list is provided, buildify will create an external build with each module in the list. By default the bundle will be written to the same path as the build outfile with -externals.js appended to the file name e.g.

given app/assets/app.js

The externals will be written to app/assets/app-externals.js

Running tests

npm test

Example

see example for a working example.

in package.json


{
  ....
  "scripts" : {
    "build" : "bundbi app"
  },
  "browserify" : {
    "transform" : ["babelify"],
    "extensions" : [
      ".jsx"
    ],
    "build" : {
      "app" : {
        "main" : "src/app.js",
        "outfile" : "../app/assets/app.js",
        "external" : [
          "flux",
          "events"
        ]

      }
    }
  }
}

then

$ npm run build

Todo

  • [ ] common externals
  • [ ] common external resolution with build level externals e.g. keep external bundles DRY
  • [ ] allow for custom paths for external bundles