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

nodeinjection

v0.0.5

Published

A node.js framework to help you build your own dependency injection framework. It is leaned towards angularjs' dependency injection style.

Readme

#nodeInjection lightweight helper to create your own node.js dependency injection. It resolves dependencies only on-demand and asynchronously.

##Initialization

//require and initialize
require('nodeinjection')(function(ni) {

	//load all node.js core modules as dependencies
    ni.registry.loadCoreModules();

    //add paths ni should initialize for you
    ni.addPath(__dirname, "controller");
    ni.addPath(__dirname, "service");

    //the object returned in this function will be your "application" object
    return new App(ni);
});

##Application object overrides

You can override behaviour by defining certain methods in the application object you provide during initialization

method | parameters | returns | description ------------- | -------------- | ------- | ---------- loadFile | path (string) | void | gets called whenever a file should be loaded. If you define this method, you have to do the loading yourself.

##Application object example

Here is an example how to get angular-style dependency injection

/**
 * Creates a new App object
 * @param {NodeInjection} ni
 * @constructor
 */
var App = function(ni) {
    this._ni = ni;
};

/**
 * Register a service
 * @param {string} name
 * @param {...string} dependency
 * @param {function} factory
 */
App.prototype.service = function(name, dependency, factory) {
    if(arguments.length < 2) {
        throw new Error("You must provide at least two parameters, a name and a factory function.");
    }else{
        if(typeof (arguments[0]) !== 'string') {
            throw new Error("First parameter must be a string");
        }

        if(typeof (arguments[arguments.length - 1]) !== 'function') {
            throw new Error("Last parameter must be a factory function");
        }
    }

    factory = arguments[arguments.length - 1];
    var dependencies = Array.prototype.splice.call(arguments, 1, arguments.length - 2);

    this._ni.registry.register(name, dependencies, factory);
};

/**
 * Build a controller
 * @param {...string} dependency
 * @param {function} factory
 */
App.prototype.controller = function(dependency, factory) {
    var dependencies = Array.prototype.splice.call(arguments, 0, arguments.length - 1);
    factory = arguments[arguments.length - 1];
    if(typeof (factory) !== 'function') {
        throw new Error("Last parameter must be a factory function");
    }

    this._ni.compose(dependencies, factory);
};

// ----- method overrides -----

/**
 * Overrides NI's file loading behaviour
 * @param {string} path
 */
App.prototype.loadFile = function(path) {
    console.log('loading', path);
    require(path)(this);
};

##Your code files

NI then assumes each file in your specified paths returns a closure like shown below and provides you with your app object. You can override this behaviour by defining an loadFile method in your application object (see overrides).

module.exports = function(app) {

};

you can find more examples in the examples folder.

##Licence MIT