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 🙏

© 2024 – Pkg Stats / Ryan Hefner

dependencyinjection

v1.3.0

Published

a simple dic

Downloads

25

Readme

Dependecy Injection Container for Node

A simple DIC and ServiceLocator based heavily on the Symfony DI Component.

Concepts

A container loads a requested service using a given ServiceLocator.

FileLoaders configure the containers for a set of Services.

But, we have require/import/whatever, right?

Differences with require and it's ../ hell

A small lists, because lists are cool:

  • require does not support alias
  • require does not support parameter binding
  • require tends to be a pain in the *ss with it's relative paths
  • require kind of enforces tight coupling of implementations

Installation

npm install dependencyinjection --save

Usage

Start by Creating a simple service, e.g. in the folder moduleA:

// @file moduleA/Service.js
function Service(message) {
    this.message = message;
}

Service.prototype = {
    test: function test() {
        console.info(this.message);
    }
}

module.exports = Service;

Now we have created our Service, we will add the service to our JSON definition file:

// @file moduleA/services.json
{
  "services": {
    "myService": {
      "module": "Service",
      "arguments": ["%foo"]
    }
  }
}

Notice how we define an argument that is a parameter called foo. For more info see ServiceDefinition

Let's add this parameter to our container definition:

// @file moduleA/services.json
{
  "parameters": {
    "foo": "bar"
  },
  "services": {
    "myService": {
      "module": "Service",
      "arguments": ["%foo"]
    }
  }
}

Now that we have defined our services, we need to fire up the container, and let the JsonFileLoader do it's job:

import DIC from dependencyinjection;

const container = new DIC.Container(new DIC.ServiceLocator());
const loader = new DIC.JsonFileLoader(container);
loader.loadFile('ModuleAlias', __dirname + '/ModuleA/services.json')

That's it, you can now start using your services:


const myService = container.get('ModuleAlias/myService');
myService.test(); // will log "bar" to console.info

Documentation

Roadmap

  • cool stuff

Author

  • Jeroen "pinoniq" Meeus