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

multiple-builds

v0.1.1

Published

Adds the Abbility to generate multiple build files of your components

Downloads

10

Readme

Multiple-builds

Adds the Abbility to generate multiple outputs for the component builder.

When you build a large application, most of the time you have a website to show off your product and then the application itself. The majority of your code obviously belongs to your core application because thats where most of the interaction happens. So it makes sense to have two build files corresponding to those almost completely different pages. Component's builder doesn't have that feature implemented.

Installation

$ npm install multiple-builds

Usage

Add a build property to your component.json file for each major component from which you want to have a seperate build

{
  ...
  "build": "site"
  ...
}

In your normal build process you can now build those major components with their dependencies

build/builder.js

var Builder = require('component-builder'),
    multiple = require('multiple-builds'),
    templates = require('./templates'),
    styles = require('./styles')

module.exports = function( req, res, next ) {
  new Builder('.')
    .use( templates )
    .use( styles )
    .use( multiple )
    .build( 'site', 'public/site' )
    .build( 'account', 'public/account' )

  next()
}

This will output two independent builds:

- public
- - site.js
- - site.css
- - account.js
- - account.css

API

.build( name:String, path:String )

name must be identical to the build property in your component.json