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

build.js

v0.3.0

Published

Downloads

33

Readme

Basement = node.js web pipeline

Basement target is to simpify life to frontend developers. Idea comes from Ruby driven project called rake pipeline. You are allowed to define your file processing in a declarative way, in order to automate your build system for your frontend application.

Because basement, can be integrated to any node.js application, its target is to extend your reach within your one and only development server, without need to spawn any other tool.

How does it work?

The system watch in a given location, once you specify in your pipeline configuration. Each time you create / update / delete the file, its content is reloaded and together with other loaded files pipeline processing is invoked. In order to customize its behavior, you are able to build it up from couple predefined filters.

How to start?

Installation with npm is easy as:

npm install basement

Then anywhere in your application create a pipeline definition. If you write Ember.js app with handlebars templates, it might look like this:

Pipeline = require('basement').Pipeline;
ClosureFilter = require('basement').ClosureFilter;
ConcatFilter = require('basement').ConcatFilter;
HandlebarsCompileFilter = require('basement').HandlebarsCompileFilter;

new Pipeline({
  input: 'frontend/lib',
  output: 'application.js',
  pattern: '*.js',

  filters: [
    new ClosureFilter(),
    new ConcatFilter({
      separator: '\n\n'
    })
  ]
})

new Pipeline({
  input: 'frontend/lib/templates/',
  output: 'application.templates.js',
  pattern: '*.handlebars',

  filters: [
    new HandlebarsCompileFilter(),
    new ConcatFilter({
      separator: '\n'
    })
  ]
})

The definition should be self descripting. Per pipeline you specify input folder and output file and a pattern, which is used to filter only specific files. Pattern might also look for instance like *_test.js to compile your tests together.

The list of filters is executed in a specific order.

Extend with your own filters

The simpliest filter which just proxy content, without any modification might look like this.

module.exports = MyFilter = function(options) {}

MyFilter.prototype.process = function(data) {
  for(var i in data) {
    data[i] = data[i]
  }

  return data;
}