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

colle

v0.1.5

Published

A Nodejs dependency injection library

Readme

colle

Build Status

A simple Nodejs dependency injection framework inspired by Angularjs. I build this framework to be used in conjunction with coffescript's programs where everything is compiled in a single js file; so I don't have to worry about compilation order. Also I believe it can be reused for other cases...

Installation

npm install colle

Usage

Create an injector

call the make function, the result should be reused globally.

colle = require('colle').make();

Add dependencies

call the set function with the following parameters to create a dependency:

  1. a name
  2. an array of dependencies
  3. a constructor function taking denpendecies as parameters The result of the constructor will be injected.

An exemple for an injector that create a counter that do not take dependencies:

colle.set("counter", [], function() {
    var _value = 0;
    return {
        addOne: function() {
            _value += 1;
        },
        value: _value
    };
});

A injector to print the counter dependency.

colle.set("print", ["counter"], function(counter) {
    return function() {
      console.log(counter.value);
    };
});

Init function

Sometimes construction can fail (like the connection to a database). You can define an _init function that takes a callback to report the error:

colle.set("db", [], function() {
    var db = null;
    
    var _init = function(cb) {
        connectDb(function(error, instance) {
            if (error)
                return cb(error); // some error!
            db = instance;
            cb(null); // ok, everything is fine!
        });
    };
    
    return {
        db: db
        _init: _init
    };
});

Note that when a dependency failed to start properly the whole process is halted.

Starting

At the end of the program call the start method to setup all the contructors in the right order (if a cyclic dependency is detected, an exception will be thown):

colle.start(function(err) {
    if (err)
    	return console.log "something wrong happend: " + err;
    console.log "dependencies are ready!";
    counter = colle.get("counter");
    counter.addOne();
    console.log(counter.value);
};

Inside the start function call the get method to get a dependency.