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 🙏

© 2025 – Pkg Stats / Ryan Hefner

inji

v0.0.2

Published

Angular like dependency injection for nodejs

Readme

Angular like dependency injection for NodeJS.


Installation

npm i --save inji

Usage

// Load Module 
const inji = require("inji");
// Add Value
inji.value("ValueName", Value);

// Add Service
inji.service("ServiceName", [ServiceFunction]);

// Add Factory
inji.factory("FactoryName", [FactoryFunction])

Just like angular js, factory objects will be singleton. That means it will only created when its called. But services will be crated every time it needed.

Example :



// index.js
const inji = require("inji");

inji.value("Config", {
    "text" : "This is a test message"
});

// Every paremeter before factory function will be injected. 
// Config will be injected to LogFactory function in this case.
inji.factory("LogFactory", ["Config", require("./LogFactory.js")]);


// Not only in in index.js, you can reach any object from anywhere after adding it.
// There are two ways to reach objects. 
// First options is inji.get() function
var Config = inji.get("Config");
// or
var LogFactory = inji.get("LogFactory");


// The other way is inji.invoke() function.
// Instead of getting all injections oen by one with inji.get()
inji.invoke(["Config", "LogFactory", function (Config,LogFactory) {
    LogFactory.print(); // "This is a test message"
}])

// LogFactory.js

function LogFactory (Config){

    // Intead of getting Config with inji.get("Config") here,
    // it is better inject all dependencies when you define this factory object.

    var vm = this;

    vm.print = () =>{
        console.log(Config.text);
    }
}

module.exports = LogFactory

For better project management, you can set your injections in a seperate file.

// index.js
const inji = require("inji");
inji.load("./injections.js"); // or require("./injections.js") is same with load function.

inji.invoke(["LogicFactory", function (LogicFactory){
    LogicFactory.start();
}])
// index.js
const inji = require("inji");
var config = require('config.json')

inji.value("Config", config("./config.json"));

inji.factory("LogFactory", ["Config", require("./pathToLogFactory")]);
inji.service("SocketService", ["LogFactory", require("./pathToSocketService")]);
inji.factory("LogicFactory", ["LogFactory", "SomeService", require("./pathToLogicFactory")]);