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

compartment

v0.3.0

Published

A type of dependency graph, component manager, and package builder.

Readme

Compartment v0.3.0

Compartment is part dependency graph, part component manager, part package builder, all handled through a manifest file. The manifest simply stores a list of components and their dependency on other components from the same manifest. Compartment provides an easy mechanism to create custom packaging builds with resolution for file types, system paths, and requirements.

Intro

Compartment was built to handle the dependencies for front-end files, like CSS and JS. It allows components to define source paths for multiple file types, making it really easy to customize and package. However, Compartment is pretty abstract and can be used in any way possible.

Usage

Require the module and instantiate a new instance.

var Compartment = require('compartment'),
    graph = new Compartment();

Define the types of files the graph will support.

graph.addTypes({
    css: '/src/css/',
    js: '/src/js/'
});

Either load the list of components from a manifest file, or define manually. Each component supports the following properties:

  • name - Name of component
  • category - The type of component
  • require - A list of other components that this component requires
  • provide - A list of other components that this component includes
  • priority - The order in which to sort components in the chain
  • source - An object mapping of types (defined above) to a list of values
graph.loadManifest('path/to/manifest.json');

graph.addComponents({
    button: {
        category: 'component',
        source: {
            css: ['button.css']
        }
    },
    buttonGroup: {
        category: 'component',
        require: ['button'],
        source: {
            css: ['button-group.css']
        }
    },
    modal: {
        category: 'component',
        source: {
            css: ['modal.css'],
            js: ['modal.js']
        }
    }
});

Build a chain of components (or all) with optional category filtering.

graph.buildChain(); // all
graph.buildChain(['buttonGroup']); // build buttonGroup and dependencies
graph.buildChain(null, 'component'); // filter all by category

Return a merged list of sources based on the type.

graph.buildChain(['buttonGroup']).getPaths('css');
// ['/src/css/button.css', '/src/css/button-group.css']

Running Tests

Run the following command in the project root to run all tests.

mocha