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

bem-pack

v0.1.0

Published

Pack node-style source files from a stream of path's into a browser bundle

Readme

bem-pack

NPM version Build Status Coverage Status Dependency Status

Pack node-style source files from a stream of path's into a browser bundle with require layering support.

Note: This plugin is highly sensitive to order, in which you call add method.

Usage

var bempack = require('bem-pack');
var pack = bempack();

pack.add('base/base.js');
    .add('main/base.js');
    .bundle(function (err, buf) {
        console.log(buf.toString());
    });

Require layering

This feature is really handy, when you want to achieve flexible extension of javascript files, that not exported in modules. In normal world to extend some base module you possible create myBase module and require base constructor from myBase constructor:

// base.js
module.exports = 'base';

// myBase.js
module.exports = require('./base.js') + ' extended!';

But in BEM world you have same filename for javascript file in different layers of definition (or directoires):

// base/base.js
module.exports = 'base';

// site/base.js
module.exports = require('./base.js') + ' extended!';

As you can see, snippet above will not work properly, because you should fix the path of the require call. Ofter there is no way to do this, because order of layers can change eventually. So we come up with this idea:

Every bundled file will "export" module with it BEM identifier.

For example base__elem.js will export base__elem module, that can be required in next bundled javascript file:

// base/base.js
module.exports = 'base';

// site/base.js
module.exports = require('base') + ' extended!';

This is not stable way of doing layered requires, but it seems nice and simple to implement.

API

bem-pack([options])

Returns instance of browserify with additional step added to deps pipeline.

options

All options are passed to browserify constructor, except ignoreMissing is setted to true always.

naming

Type: Function

Function, that will generate some kind of export name for given path. By default we split filename by . and take first part. For our usage cases it will contain BEM identificator.

License

MIT (c) 2014 Vsevolod Strukchinsky